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 abrezovsky, christian.heimes, eryksun, giampaolo.rodola, jgosmann, mhils, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-03-06.00:49:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551833389.36.0.242005823275.issue29515@roundup.psfhosted.org>
In-reply-to
Content
The problem is that if we add lots of new constants in 3.7.3, code written in that version very easily becomes incompatible with 3.7.2 and earlier. So we don't like making changes like that.

If we know which ones are "normally" defined on Linux machines, where specifying them on Windows will make it just work, then I'd just add those ones.

Anything that is Windows-specific (if any?) or that may cause applications to break if they're testing for the constant but it doesn't work smoothly should not go back to 3.7.
History
Date User Action Args
2019-03-06 00:49:49steve.dowersetrecipients: + steve.dower, paul.moore, giampaolo.rodola, christian.heimes, tim.golden, zach.ware, eryksun, jgosmann, mhils, abrezovsky
2019-03-06 00:49:49steve.dowersetmessageid: <1551833389.36.0.242005823275.issue29515@roundup.psfhosted.org>
2019-03-06 00:49:49steve.dowerlinkissue29515 messages
2019-03-06 00:49:49steve.dowercreate