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 eric.araujo, lemburg, pitrou, r.david.murray, vstinner
Date 2010-08-13.14:15:11
SpamBayes Score 9.0601715e-10
Marked as misclassified No
Message-id <1281708914.06.0.149993700912.issue9560@psf.upfronthosting.co.za>
In-reply-to
Content
@r.david.murray, @lemburg: So, can I commit my patch?

> However, it is still possible to have that path contain weird
> characters, so the example is still valid.

It's not only a question of "weird" characters. Use case of #8611: install Python in a directory with a name not encodable to the filesystem encoding and try run Python. Install or use a Python installed in an external media like an USB key (encoding problem is not a rare problem with USB keys).

On Windows, it's quite easy to find a character not encodable to the filesystem encoding (mbcs). Eg. Ł for codepage 1252. On Linux, any non-ASCII can be used if you run Python with C locale (locale encoding: ascii).

#4352 and #8988 (Windows issues, so mbcs encoding) are directly related to #8611.
History
Date User Action Args
2010-08-13 14:15:14vstinnersetrecipients: + vstinner, lemburg, pitrou, eric.araujo, r.david.murray
2010-08-13 14:15:14vstinnersetmessageid: <1281708914.06.0.149993700912.issue9560@psf.upfronthosting.co.za>
2010-08-13 14:15:12vstinnerlinkissue9560 messages
2010-08-13 14:15:11vstinnercreate