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 vstinner
Recipients Jan Niklas Hasse, abarry, ezio.melotti, lemburg, methane, ncoghlan, r.david.murray, vstinner
Date 2016-12-16.15:12:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Victor>> I proposed to add "-X utf8" command line option for UNIX to force utf8 encoding. Would it work for you?

Jan Niklas Hasse> Unfortunately no, as this would mean I'll have to change all my python invocations in my scripts and it wouldn't work for executable files with "#!/usr/bin/env python3" would it?

Usually, when a new option is added to Python, we add a command line option (-X utf8) but also an environment variable: I propose PYTHONUTF8=1.

Use your favorite method to define the env var "system wide" in your docker containers.

Note: Technically, I'm not sure that it's possible to support -E option with PYTHONUTF8, since -E comes from the command line, and we first need to decode command line arguments with an encoding to parse these options.... Chicken-and-egg issue ;-)
Date User Action Args
2016-12-16 15:12:22vstinnersetrecipients: + vstinner, lemburg, ncoghlan, ezio.melotti, r.david.murray, methane, abarry, Jan Niklas Hasse
2016-12-16 15:12:22vstinnersetmessageid: <>
2016-12-16 15:12:22vstinnerlinkissue28180 messages
2016-12-16 15:12:22vstinnercreate