[Python-Dev] provisional status for asyncio

Gustavo Carneiro gjcarneiro at gmail.com
Fri Aug 28 20:44:10 CEST 2015

On 28 August 2015 at 17:11, Yury Selivanov <yselivanov.ml at gmail.com> wrote:

> On 2015-08-28 11:44 AM, Brett Cannon wrote:
>>     Unfortunately, separating it from the standard library is something
>>     that I don't think we can do so late in the 3.5 release candidates
>>     process.
>> Ultimately it's Larry's call, but I don't see why we couldn't. If we were
>> talking about something as low-level as the urllib package then I would
>> agree, but beyond its own tests is there anything in the stdlib that
>> depends on asyncio?
> As Victor already replied, asyncio is pretty self contained, and
> nothing in the stdlib depends on it.
> If we really can remove it, let's consider it.

-1 for removing it.  It is way too late for 3.5 IMHO.  You should have
proposed it at least 6 months ago.  This feels too rushed.

+1 for changing sys.path to allow pip-installed asyncio to override the
stdlib version (for 3.6).  Some developers complain that NodeJS's packaging
system is better that Python, maybe this lack of flexibility is one of the

Gustavo J. A. M. Carneiro
Gambit Research
"The universe is always one step beyond logic." -- Frank Herbert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150828/d7364035/attachment.html>

More information about the Python-Dev mailing list