[Python-Dev] provisional status for asyncio
Larry Hastings
larry at hastings.org
Sat Aug 29 19:36:33 CEST 2015
More information about the Python-Dev mailing list
Sat Aug 29 19:36:33 CEST 2015
- Previous message (by thread): [Python-Dev] provisional status for asyncio
- Next message (by thread): [Python-Dev] provisional status for asyncio
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 08/28/2015 08:44 AM, Brett Cannon wrote: > On Fri, 28 Aug 2015 at 08:35 Yury Selivanov <yselivanov.ml at gmail.com > <mailto:yselivanov.ml at gmail.com>> 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? I'm flexible here. My concern is shipping high-quality software. Removing an entire package outright, even at such a late date, is pretty low-risk. But before I'd allow it, you'd have to get a BDFL pronouncement (or BDFL-delegate pronouncement). //arry/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20150829/0cd66cca/attachment.html>
- Previous message (by thread): [Python-Dev] provisional status for asyncio
- Next message (by thread): [Python-Dev] provisional status for asyncio
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list