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 ncoghlan
Recipients Jan Niklas Hasse, Sworddragon, abarry, akira, barry, ezio.melotti, lemburg, methane, ncoghlan, r.david.murray, vstinner, yan12125
Date 2017-01-05.12:41:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1483620110.56.0.870517187115.issue28180@psf.upfronthosting.co.za>
In-reply-to
Content
The trade-offs here are incredibly complex (and are mainly a matter of deciding whose code and configurations we want to break in 3.7+), so I think competing PEPs are going to be better than attempting to create a combined PEP that tries to cover all the options.

That way each PEP can argue as strongly as it can for the respective authors preferred approach to tackling the default C locale problem, even if they point to a common background section in one of the PEPs (similar to the way PEPs 522 and 524 shared a common problem definition, even though they proposed different ways of handling it).
History
Date User Action Args
2017-01-05 12:41:50ncoghlansetrecipients: + ncoghlan, lemburg, barry, vstinner, ezio.melotti, r.david.murray, methane, akira, Sworddragon, yan12125, abarry, Jan Niklas Hasse
2017-01-05 12:41:50ncoghlansetmessageid: <1483620110.56.0.870517187115.issue28180@psf.upfronthosting.co.za>
2017-01-05 12:41:50ncoghlanlinkissue28180 messages
2017-01-05 12:41:50ncoghlancreate