[Python-Dev] Status of PEP 3145 - Asynchronous I/O for subprocess.popen

Glenn Linderman v+python at g.nevcal.com
Fri Mar 28 21:35:31 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 3/28/2014 11:35 AM, Josiah Carlson wrote:
>
>     If it were me, I'd define three methods, with longer names to
>     clarify what they do, e.g.
>
>     proc.write_nonblocking(data)
>     data = proc.read_nonblocking()
>     data = proc.read_stderr_nonblocking()
>
>
> Easily doable.

I'd appreciate being notified if you do update/test as described.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140328/5ebe954e/attachment-0001.html>

---

• 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