This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author yselivanov
Recipients aeros, asvetlov, petr.viktorin, yselivanov
Date 2020-06-09.18:06:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1591725987.09.0.739615100876.issue40802@roundup.psfhosted.org>
In-reply-to
Content
> Since asyncio is no longer provisional, should it break backwards compatibility with just a What's New entry?

Adding new APIs to asyncio can't be classified as a backward compatibility issue. Otherwise the development of it would stall and nobody would benefit from it. uvloop and anyio will be eventually updated to support new APIs, I don't see any problem here.
History
Date User Action Args
2020-06-09 18:06:27yselivanovsetrecipients: + yselivanov, petr.viktorin, asvetlov, aeros
2020-06-09 18:06:27yselivanovsetmessageid: <1591725987.09.0.739615100876.issue40802@roundup.psfhosted.org>
2020-06-09 18:06:27yselivanovlinkissue40802 messages
2020-06-09 18:06:27yselivanovcreate