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 doerwalter, ezio.melotti, lemburg, ncoghlan, python-dev, serhiy.storchaka, vstinner
Date 2013-11-23.01:03:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> Regarding UTF-8 et al, the existing shortcuts in unicodeobject.c already
> bypass the full codec machinery, and that includes the exception wrapping
> on failures.

There are still platforms using locale encodings different than ascii,
latin1 or utf8. For example, Windows never uses these encodings for
ANSI or OEM code page. ANSI code page is used as the Python filesystem
encoding which is used in a lot of places. OEM code page is used for
the stdio streams (stdin, stdout, stderr). There are some users using
locales with the latin9 encoding.

I proposed to remove the new code for exception handling to simplify
the code (because the error should not occur anymore).
Date User Action Args
2013-11-23 01:03:19vstinnersetrecipients: + vstinner, lemburg, doerwalter, ncoghlan, ezio.melotti, python-dev, serhiy.storchaka
2013-11-23 01:03:19vstinnerlinkissue19619 messages
2013-11-23 01:03:19vstinnercreate