On 30 August 2015 at 05:16, Yury Selivanov <yselivanov...@gmail.com> wrote: > Since there is at least some possibility that we might have another > discussion about asyncio removal from the stdlib in 3.6, should I > just reuse the warning we had in 3.4 for asyncio: > > > Note: The asyncio package has been included in the > standard library on a provisional basis. Backwards > incompatible changes (up to and including removal > of the module) may occur if deemed necessary by the > core developers. > > ?
I don't see much chance of us actually removing it - the most I see us doing is potentially shifting to a "bundled 3rd party library" update model if there's still a high churn rate in the API after another release cycle. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ 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
