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 njs
Recipients asvetlov, malin, methane, ned.deily, njs, paul.moore, skn78, steve.dower, thatiparthy, tim.golden, tjguk, zach.ware
Date 2018-02-06.07:44:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm sympathetic to the idea that we don't want to carry around these checks, but also to the idea that this caused a regression in a micro release and that's not cool. Hence the idea that maybe we should keep everything the way it is in 3.7, but disable the new constants in 3.6, so that it arrives as part of a major release.

OTOH it's been in 3.6 for like 6 weeks already so I guess a lot of the affected parties are already working around it.
Date User Action Args
2018-02-06 07:44:33njssetrecipients: + njs, paul.moore, tim.golden, ned.deily, asvetlov, methane, zach.ware, steve.dower, thatiparthy, malin, tjguk, skn78
2018-02-06 07:44:33njssetmessageid: <>
2018-02-06 07:44:33njslinkissue32394 messages
2018-02-06 07:44:33njscreate