➜

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 steve.dower
Recipients jdemeyer, ncoghlan, petr.viktorin, scoder, steve.dower, vstinner
Date 2019-06-19.17:24:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560965088.83.0.927066489316.issue37250@roundup.psfhosted.org>
In-reply-to
Content 
If we should put in the workaround for 3.8, how does that make it okay to remove in 3.9? It's been deprecated since 3.0 already, so if we can't remove it after eight releases, I don't see how it's consistent to remove it after a ninth. Once we put it back, it basically has to stay.

The middle ground doesn't make sense. We should either replace it with the new field, or put the new field at the end and leave the deprecated one exactly as it was.
History
Date User Action Args
2019-06-19 17:24:48steve.dowersetrecipients: + steve.dower, ncoghlan, scoder, vstinner, petr.viktorin, jdemeyer
2019-06-19 17:24:48steve.dowersetmessageid: <1560965088.83.0.927066489316.issue37250@roundup.psfhosted.org>
2019-06-19 17:24:48steve.dowerlinkissue37250 messages
2019-06-19 17:24:48steve.dowercreate