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 amaury.forgeotdarc, loewis, vstinner
Date 2011-10-19.18:25:32
SpamBayes Score 6.311618e-14
Marked as misclassified No
Message-id <1319048733.47.0.680537139866.issue13216@psf.upfronthosting.co.za>
In-reply-to
Content
> > Sorry, which bug?

> #6501 and friends

Hum, this particular issue, #6501, doesn't concern the code page 65001. The typical usecase (issues #7441 and #10920) is:
------------
C:\victor\cpython>chcp 65001
Page de codes active : 65001

C:\victor\cpython>pcbuild\python_d.exe
Fatal Python error: Py_Initialize: can't initialize sys standard streams
LookupError: unknown encoding: cp65001
------------

The console and console output code pages may be changed by something else.

The current workaround is to set PYTHONIOENCODING environment variable to utf-8, but as explained in msg132831, the workaround is not applicable if Python is embeded or if the program has been frozen by cx-freeze ("cx-freeze deliberately sets Py_IgnoreEnvironmentFlag").

--

The issue #6501 was a bug in io.device_encoding(). I fixed it in Python 3.3 and I'm waiting... since 5 months... for Graham Dumpleton before backporting the fix. The issue suggests also to not fail if the encoding cannot be found (I dislike this idea).
History
Date User Action Args
2011-10-19 18:25:33vstinnersetrecipients: + vstinner, loewis, amaury.forgeotdarc
2011-10-19 18:25:33vstinnersetmessageid: <1319048733.47.0.680537139866.issue13216@psf.upfronthosting.co.za>
2011-10-19 18:25:32vstinnerlinkissue13216 messages
2011-10-19 18:25:32vstinnercreate