➜

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 asvetlov
Recipients aeros, asvetlov, miss-islington, serhiy.storchaka, xtreak, yselivanov
Date 2019-10-27.08:47:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572166070.59.0.244129300307.issue34790@roundup.psfhosted.org>
In-reply-to
Content 
> If we add the deprecation warning just for 3.9, would the removal release also be pushed forward? 

Yes, deprecating in 3.9 with removal in 3.11 is fine.

Regarding 3.8 release notes update -- not sure if it is needed flr docs-only change.

In the current situation, we have so-called *soft deprecation*: bare coroutines are deprecated in docs without any code change. This is perfectly fine, we give our users extra time to prepare for changes.
History
Date User Action Args
2019-10-27 08:47:50asvetlovsetrecipients: + asvetlov, serhiy.storchaka, yselivanov, miss-islington, xtreak, aeros
2019-10-27 08:47:50asvetlovsetmessageid: <1572166070.59.0.244129300307.issue34790@roundup.psfhosted.org>
2019-10-27 08:47:50asvetlovlinkissue34790 messages
2019-10-27 08:47:50asvetlovcreate