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 benjamin.peterson, terry.reedy, vstinner
Date 2010-10-15.22:04:54
SpamBayes Score 6.02086e-06
Marked as misclassified No
Message-id <1287180296.5.0.930149495777.issue10114@psf.upfronthosting.co.za>
In-reply-to
Content
#6543 changed code->co_filename encoding from filesystem encoding+surrogateescape to utf-8+strict.

With my patch, compile('', '\udcc3\udca9', 'exec').co_filename gives 'é', it doesn't depend on the filesystem encoding. But 'é' cannot be used with all filesystem encodings, eg. with ascii locale encoding (C locale), use it raises an error.

I now think that it was a bad idea to use utf-8 instead of the fileystem encoding. All filenames should use the filesystem encoding in Python.
History
Date User Action Args
2010-10-15 22:04:56vstinnersetrecipients: + vstinner, terry.reedy, benjamin.peterson
2010-10-15 22:04:56vstinnersetmessageid: <1287180296.5.0.930149495777.issue10114@psf.upfronthosting.co.za>
2010-10-15 22:04:54vstinnerlinkissue10114 messages
2010-10-15 22:04:54vstinnercreate