Author aeros
Recipients aeros, asvetlov, miss-islington, serhiy.storchaka, xtreak, yselivanov
Date 2019-10-27.07:25:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572161151.82.0.039178476058.issue34790@roundup.psfhosted.org>
In-reply-to
Content
> I think we can add `DeprecationWarning` for 3.9.

If we add the deprecation warning just for 3.9, would the removal release also be pushed forward? 

> Honestly, we just missed the issue when were prepared for 3.8

Yeah that's definitely understandable, there were quite a number of major changes made in 3.8. It was the first time I saw a deprecation clearly documented in a final release that didn't have an associated deprecation warning. 

As for 3.8, I would like to update the whatsnew entry to add a link to this bpo issue if that's okay, as it does not at the moment. I recently included the entry in a PR that added entries for multiple significant changes for asyncio in the 3.8, but I forgot to include the bpo link (mostly because I found it in the documentation, rather than from the bpo issue).
History
Date User Action Args
2019-10-27 07:25:51aerossetrecipients: + aeros, asvetlov, serhiy.storchaka, yselivanov, miss-islington, xtreak
2019-10-27 07:25:51aerossetmessageid: <1572161151.82.0.039178476058.issue34790@roundup.psfhosted.org>
2019-10-27 07:25:51aeroslinkissue34790 messages
2019-10-27 07:25:51aeroscreate