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 eric.araujo
Recipients eric.araujo, r.david.murray, vstinner
Date 2010-10-12.17:39:45
SpamBayes Score 2.5499623e-05
Marked as misclassified No
Message-id <1286905187.25.0.0222983594214.issue10039@psf.upfronthosting.co.za>
In-reply-to
Content
> if you are saying, "the user asked for it, it *should* fail", then
> that is indeed one of the arguments put forward in issue 9992 where
> this was discussed.
You could put it that way, thanks for phrasing my thoughts :)

> But I think the emerging consensus is that it is better to just avoid
> the problem by always using the locale on Unix,
*displays his lack of knowledge* Is it always correct to decode a filename with the locale encoding on Unix?  Can’t each filesystem have its own encoding?

> and solve the problem that PYTHONFSENCODING was supposed to solve in a
> different way (by always using utf-8 on OSX and unicode on Windows).
If there is a better alternate way, let’s go for it, and maybe remove PYTHONFSENCODING altogether, since it’s new in 3.2.

Thanks for explaining!  I’ll repay your time by reviewing the doc patches.
History
Date User Action Args
2010-10-12 17:39:47eric.araujosetrecipients: + eric.araujo, vstinner, r.david.murray
2010-10-12 17:39:47eric.araujosetmessageid: <1286905187.25.0.0222983594214.issue10039@psf.upfronthosting.co.za>
2010-10-12 17:39:45eric.araujolinkissue10039 messages
2010-10-12 17:39:45eric.araujocreate