[issue10952] Don't normalize module names to NFKC?

[Alexander Belopolsky]

Alexander Belopolsky <belopolsky at users.sourceforge.net> added the comment:

On Wed, Jan 19, 2011 at 9:21 PM, STINNER Victor <report at bugs.python.org> wrote:
..
> New problem: if the parser doesn't normalize module names on import, it does still
> normalize module names on other instructions.
>
> Example: "import \xB5Torrent; del \xB5Torrent" raises an error on del because the parser
> normalized del identifier (the second module name) => "import \xB5Torrent; del \u03BCTorrent".
>

This won't be a problem if you make "import \xB5Torrent" behave as
"\xB5Torrent = __import__('\xB5Torrent')".  The latter is equivalent
to "\u03BCTorrent =  __import__('\xB5Torrent')".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10952>
_______________________________________