[Python-Dev] Status of PEP 3145 (original) (raw)
[Python-Dev] Status of PEP 3145 - Asynchronous I/O for subprocess.popen
Nick Coghlan ncoghlan at gmail.com
Wed Mar 26 00:14:02 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 26 Mar 2014 08:22, "Antoine Pitrou" <solipsis at pitrou.net> wrote:
Hi, On core-mentorship someone asked about PEP 3145 - Asynchronous I/O for subprocess.popen. I answered that asyncio now has subprocess support (including non-blocking I/O on the three standard stream pipes), so it's not obvious anything else is needed. Should we change the PEP's status to Rejected or Superseded?
Yes. I think we'd typically use Rejected in this case, as Superseded normally relates to the evolution of interface definition PEPs.
Cheers, Nick.
Regards Antoine.
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140326/c056f6cb/attachment.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 ]