That would be a rather strong unilateral decision. Why don't you ask the authors? In theory the PEP's proposals could serve in situations where asyncio isn't appropriate, and asyncio's subprocess I/O isn't the smoothest API imaginable. (In practice I'm not sure if the PEP would have been written with asyncio subprocess support in place.)
On Tue, Mar 25, 2014 at 3:19 PM, Antoine Pitrou <solip...@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? > > Regards > > Antoine. > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com