Message135755
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 :-) |
|
Date |
User |
Action |
Args |
2011-05-10 23:04:44 | vstinner | set | recipients:
+ vstinner, tarek, eric.araujo, zegreek, nils |
2011-05-10 23:04:44 | vstinner | set | messageid: <1305068684.08.0.750782613492.issue6011@psf.upfronthosting.co.za> |
2011-05-10 23:04:43 | vstinner | link | issue6011 messages |
2011-05-10 23:04:43 | vstinner | create | |
|