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, nils, tarek, vstinner, zegreek
Date 2011-05-10.23:04:43
SpamBayes Score 1.1923795e-13
Marked as misclassified No
Message-id <1305068684.08.0.750782613492.issue6011@psf.upfronthosting.co.za>
In-reply-to
Content
I fixed #10419 in Python 3.2 and 3.3 (I applied my copy_script-2.patch fix). It is now possible to compile and install Python 3.2 and 3.3 with a non-ASCII prefix, so this issue can be done.

If you have issues when compiling Python with a non-ASCII prefix (and a locale encoding different than UTF-8), reopen the issue or open a more specific issue.

--

I don't want to backport fixes of this issue to Python 3.1, because Python 3.1 requires too much effort to handle correctly non-ASCII paths (not only for this specific issue). I consider that Python 3.1 is a stable release and should not be touched too much and non-ASCII path with a locale encoding different than UTF-8 is a corner case. If you have this issue with Python 3.1, please upgrade to Python 3.2 :-)
History
Date User Action Args
2011-05-10 23:04:44vstinnersetrecipients: + vstinner, tarek, eric.araujo, zegreek, nils
2011-05-10 23:04:44vstinnersetmessageid: <1305068684.08.0.750782613492.issue6011@psf.upfronthosting.co.za>
2011-05-10 23:04:43vstinnerlinkissue6011 messages
2011-05-10 23:04:43vstinnercreate