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 serhiy.storchaka
Recipients benjamin.peterson, ezio.melotti, lemburg, ncoghlan, serhiy.storchaka, vstinner
Date 2017-12-30.16:26:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In Python 2.7 setting PYTHONIOENCODING=undefined mostly works as expected.

$ PYTHONIOENCODING=undefined python -c 'print(123)'
$ PYTHONIOENCODING=undefined python -c 'print("abc")'
$ PYTHONIOENCODING=undefined python -c 'print(u"abc")'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/encodings/", line 19, in encode
    raise UnicodeError("undefined encoding")
UnicodeError: undefined encoding

Most tests (except test_doctest and test_gdb) are passed with PYTHONIOENCODING=undefined.

But in Python 3 setting PYTHONIOENCODING=undefined seems just silently terminates the interpreter (exited with code 1).
Date User Action Args
2017-12-30 16:26:14serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, ncoghlan, vstinner, benjamin.peterson, ezio.melotti
2017-12-30 16:26:14serhiy.storchakasetmessageid: <>
2017-12-30 16:26:14serhiy.storchakalinkissue32456 messages
2017-12-30 16:26:13serhiy.storchakacreate