[Python-Dev] Status of PEP 3145
[Python-Dev] Status of PEP 3145 - Asynchronous I/O for subprocess.popen
Paul Moore p.f.moore at gmail.comFri Mar 28 09:09:45 CET 2014
- Previous message: [Python-Dev] Status of PEP 3145 - Asynchronous I/O for subprocess.popen
- Next message: [Python-Dev] Status of PEP 3145 - Asynchronous I/O for subprocess.popen
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 28 March 2014 05:09, Josiah Carlson <josiah.carlson at gmail.com> wrote: > So yeah. Someone want to make a decision? Tell me to write the docs, I will. > Tell me to go take a long walk off a short pier, I'll thank you for your > time and leave you alone. I had a need for this a few years ago. It's messy to do on Windows (ctypes callouts to PeekNamedPipe to check if you can read from the process without blocking). So I would like to see a recipe for this, (even if it's likely to be another few years before I ever need it again :-)). Paul
- Previous message: [Python-Dev] Status of PEP 3145 - Asynchronous I/O for subprocess.popen
- Next message: [Python-Dev] Status of PEP 3145 - Asynchronous I/O for subprocess.popen
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list