[issue11230] "Full unicode import system" not in 3.2

Serhiy Storchaka added the comment: Python 3.2 is out of maintenance. Full Unicode path support was added in Python 3.3 by issue3080. -- nosy: +serhiy.storchaka resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue11230] "Full unicode import system" not in 3.2

STINNER Victor added the comment: > The issue I'm thinking about is that the Mac HSF+ filesystem There is no issue with HFS+ normalization. The kernel "normalizes" filenames to its own variant, Python doesn't have to care about this. When you write "import h<é normalized to NFC>" or "import h

[issue11230] "Full unicode import system" not in 3.2

Tom Christiansen added the comment: Whoops, I meant that it appears that Python runs its identifiers through NFC. How that gets along with a filesystem that has quasi-NFD filenames I'm not sure, but it seems like it might be a variant of the case-insensitivity issue in filenames. --

[issue11230] "Full unicode import system" not in 3.2

Tom Christiansen added the comment: How does this work for modules that have filesystem names different from the one used for import? The issue I'm thinking about is that the Mac HSF+ filesystem keeps its Unicode filenames in (close to) NFD form. That means that a module named "caf\N{LATIN SM

[issue11230] "Full unicode import system" not in 3.2

Changes by Ned Deily : -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue11230] "Full unicode import system" not in 3.2

John added the comment: Sorry for the long delay. haypo wrote: Can you propose a sentence which is more clear about bytes/Unicode? On this page: http://www.python.org/download/releases/3.2/ is this line: "- countless fixes regarding bytes/string issues; among them full support for a bytes e

[issue11230] "Full unicode import system" not in 3.2

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue11230] "Full unicode import system" not in 3.2

STINNER Victor added the comment: >> 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 "countles

[issue11230] "Full unicode import system" not in 3.2

John added the comment: Victor asked "Which web page should updated/fixed?" Answer: The Python 3.2 download page. But what should it say? The main point is that people like me, who remember seeing a statement about this a few months ago, may expect unicode to work in every conceivable situa

[issue11230] "Full unicode import system" not in 3.2

STINNER Victor added the comment: Short answer: In Python 3.2, « import héhé » doesn't work on Windows, but you can have non-ASCII paths in sys.path. Longer answer: I fixed the import machinery to handle correctly non-ASCII characters in module *paths*. But the import machinery is unable to

[issue11230] "Full unicode import system" not in 3.2

Changes by Antoine Pitrou : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue11230] "Full unicode import system" not in 3.2

New submission from John : A few months ago I read that in 3.2 it will be possible to import modules that are located on paths containing any unicode character. (more precisely, with chars not in the local code page) After an hour or two trying to get this to work in 3.2rc3, I went looking for