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 ezio.melotti, jaysinh.shukla, mrabarnett, ncoghlan, serhiy.storchaka, vstinner
Date 2017-02-18.08:54:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1487408040.93.0.828945729319.issue29571@psf.upfronthosting.co.za>
In-reply-to
Content
Looking into this at the PyCon Pune sprints, the problem appears to be arising due to the following difference in behaviour when the unqualifed `en_IN` locale is set:

$ LANG=en_IN.UTF-8 python3 -c "import locale; print(locale.getlocale(locale.LC_CTYPE), locale.getpreferredencoding(False), sep='\n')"
('en_IN', 'UTF-8')
UTF-8

$ LANG=en_IN python3 -c "import locale; print(locale.getlocale(locale.LC_CTYPE), locale.getpreferredencoding(False), sep='\n')"
('en_IN', 'ISO8859-1')                                                                                                       
UTF-8

re.LOCALE is presumably picking up the "UTF-8" rather than the "ISO8859-1", and hence the test is failing.
History
Date User Action Args
2017-02-18 08:54:00ncoghlansetrecipients: + ncoghlan, vstinner, ezio.melotti, mrabarnett, serhiy.storchaka, jaysinh.shukla
2017-02-18 08:54:00ncoghlansetmessageid: <1487408040.93.0.828945729319.issue29571@psf.upfronthosting.co.za>
2017-02-18 08:54:00ncoghlanlinkissue29571 messages
2017-02-18 08:54:00ncoghlancreate