➜

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 docs@python, jh45, vstinner
Date 2011-03-21.01:22:19
SpamBayes Score 0.00046318525
Marked as misclassified No
Message-id <1300670542.54.0.712917776541.issue11230@psf.upfronthosting.co.za>
In-reply-to
Content 
>> Victor asked "Which web page should updated/fixed?"
> Answer: The Python 3.2 download page.

Sorry, but I don't see which page tells that Python 3.2 has a full Unicode support for import. In http://www.python.org/download/releases/3.2/, I can read "countless fixes regarding bytes/string issues; among them full support for a bytes environment (filenames, environment variables)".

"full support for a bytes environment" means that Python 3.2 has been fixed on UNIX to support undecodable filenames, but not that Python 3.2 supports unencodable filenames on Windows.

Can you propose a sentence which is more clear about bytes/Unicode?

Python 3.3 will have a full Unicode support for modules: issue #3080 is already fixed, and I think that #11619 can be fixed (maybe not easily).
History
Date User Action Args
2011-03-21 01:22:22vstinnersetrecipients: + vstinner, docs@python, jh45
2011-03-21 01:22:22vstinnersetmessageid: <1300670542.54.0.712917776541.issue11230@psf.upfronthosting.co.za>
2011-03-21 01:22:19vstinnerlinkissue11230 messages
2011-03-21 01:22:19vstinnercreate