[issue11574] Unicode Fallback Encoding on Python 3.3

STINNER Victor added the comment: TextIOWrapper is mostly based on locale.getpreferredencoding(), so msg131290 is still valid: if no env var is set, nl_langinfo() gives 'ASCII' (or something like that). But it is not easy to detect that env vars are not set. I would prefer a completly differe

[issue11574] Unicode Fallback Encoding on Python 3.3

STINNER Victor added the comment: After reading the related mail thread on python-dev, I realized that you are talking about TextIOWrapper choice (file content, not file name). My previous message is about file names. -- ___ Python tracker

[issue11574] Unicode Fallback Encoding on Python 3.3

STINNER Victor added the comment: In my experience (PYTHONFSENCODING, sys.setfilesystemencoding()): Python should just use the same encoding than the locale encoding because *all* other programs on the system use the locale encoding. If none of LANG, LC_ALL or LC_CTYPE env var is set: Python

[issue11574] Unicode Fallback Encoding on Python 3.3

Changes by Ned Deily : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue11574] Unicode Fallback Encoding on Python 3.3

Changes by Armin Ronacher : -- assignee: -> loewis nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue11574] Unicode Fallback Encoding on Python 3.3

New submission from Armin Ronacher : Right now Python happily falls back to ASCII if it can not parse your LC_CTYPE or something similar happens. Instead of falling back to ASCII it would be better if it falls back to UTF-8. Alternatively it should at least give a warning that it's falling ba