Author aeros
Recipients aeros, asvetlov, miss-islington, serhiy.storchaka, xtreak, yselivanov
Date 2019-10-27.17:15:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572196501.36.0.194286381688.issue34790@roundup.psfhosted.org>
In-reply-to
Content
> Regarding 3.8 release notes update -- not sure if it is needed flr docs-only change.

I'm not certain if the entry is necessary; my main concern is just that it's already present in the 3.8 release notes/whatsnew without anywhere to look for further information. 

> 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.

So is something considered to be a "soft deprecation" if there is no code change? If so, I may have made a mistake by specifying a release in the entry I recently added for it (https://docs.python.org/3/whatsnew/3.8.html#deprecated):

"The explicit passing of coroutine objects to asyncio.wait() has been deprecated and will be removed in version 3.10."

I would propose to adjust this to:

"The explicit passing of coroutine objects to asyncio.wait() has been deprecated. (Contributed by Yury Selivanov in :issue:`34790`.)"

Then for 3.9 whatsnew, we could specify the release:

"The explicit passing of coroutine objects to asyncio.wait() has been deprecated and will be removed in 3.11."

Thoughts?
History
Date User Action Args
2019-10-27 17:15:01aerossetrecipients: + aeros, asvetlov, serhiy.storchaka, yselivanov, miss-islington, xtreak
2019-10-27 17:15:01aerossetmessageid: <1572196501.36.0.194286381688.issue34790@roundup.psfhosted.org>
2019-10-27 17:15:01aeroslinkissue34790 messages
2019-10-27 17:15:01aeroscreate