This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | terry.reedy |
|---|---|
| Recipients | asvetlov, ezio.melotti, kbk, roger.serwy, serhiy.storchaka, terry.reedy, tshepang |
| Date | 2014年03月29日.08:44:01 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1396082641.77.0.435943972408.issue18823@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Pydev, Re: Status of PEP 3145 - Asynchronous I/O for subprocess.popen; Antoine Pitrou: > Why don't you use multiprocessing or concurrent.futures? They have > everything you need for continuous conversation between processes. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014年03月29日 08:44:01 | terry.reedy | set | recipients: + terry.reedy, kbk, ezio.melotti, roger.serwy, asvetlov, tshepang, serhiy.storchaka |
| 2014年03月29日 08:44:01 | terry.reedy | set | messageid: <1396082641.77.0.435943972408.issue18823@psf.upfronthosting.co.za> |
| 2014年03月29日 08:44:01 | terry.reedy | link | issue18823 messages |
| 2014年03月29日 08:44:01 | terry.reedy | create | |