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 loewis
Recipients asmodai, catherinedevlin, heikki, jminka, loewis
Date 2009-05-01.20:24:44
SpamBayes Score 4.26972e-05
Marked as misclassified No
Message-id <>
In-reply-to <>
> But I am curious about your thoughts about the _parse_localename()
> method being called from setlocale() raising a ValueError, whereas a
> setlocale(LC_CTYPE, "") should not fail at all, which it currently does
> if the locale in the environment is not valid.

I fail to see how this is related to this issue. In the OP's report,
the exception was locale.Error, not ValueError, and _parse_localename
isn't ever being called from setlocale() - why do you think it is being
called? AFAICT, the only callers of _parse_localename are getlocale and
getdefaultlocale (which, IMO, should both be deprecated).
Date User Action Args
2009-05-01 20:24:45loewissetrecipients: + loewis, catherinedevlin, jminka, heikki, asmodai
2009-05-01 20:24:44loewislinkissue1443504 messages
2009-05-01 20:24:44loewiscreate