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 Arfrever, eric.araujo, lemburg, pitrou, vstinner
Date 2010-09-04.00:23:35
SpamBayes Score 4.2204316e-09
Marked as misclassified No
Message-id <1283559817.19.0.284213164993.issue9632@psf.upfronthosting.co.za>
In-reply-to
Content
> In such environments you cannot expect the user to configure the
> system properly (i.e. set an environment variable).

Why would it be different for embeded python?

> Instead, the application has to provide an educated guess 
> to the Python interpreter in some way, ...

How can the application guess the encoding better than Python? If the user doesn't configure correctly its environment, I don't see how the application can get the real (correct) environment config?!

If Python is unable to start because of the filesystem encoding, it is a bug (see #8611). If Python starts but displays incorrectly filenames, it is the user fault: the user have to setup its environment.
History
Date User Action Args
2010-09-04 00:23:37vstinnersetrecipients: + vstinner, lemburg, pitrou, eric.araujo, Arfrever
2010-09-04 00:23:37vstinnersetmessageid: <1283559817.19.0.284213164993.issue9632@psf.upfronthosting.co.za>
2010-09-04 00:23:35vstinnerlinkissue9632 messages
2010-09-04 00:23:35vstinnercreate