[Python-Dev] Import and unicode: part two

Georg Brandl g.brandl at gmx.net
Wed Jan 19 22:07:03 CET 2011

Am 19.01.2011 21:32, schrieb Terry Reedy:
> On 1/19/2011 7:34 AM, Victor Stinner wrote:
>> Hi,
>> I patched Python 3.2 to support modules with non-ASCII paths (*). It
>> works well on all operating systems. But the task is not completly
>> done:
>> (a) Python 3 doesn't support non-ASCII module names (b) Python 3
>> doesn't support unencodable characters in the module path
>> I would like to know if we need to support that. Terry J. Reedy
>> wrote (issue #10828): "I think bugs in core syntax should have high
>> priority. I appreciate your work toward fixing it."
> I am a little shocked at the so-far tepid response to (a), so let me
> defend and explain my claim that it is a bug.
> In the simplest case (from 6.11. The import statement and  2.3. 
> Identifiers and keywords)
> import_stmt ::= "import" module
> module      ::= indentifier
> identifier  ::= <appropriate Unicode start and continue chars>
> There is nothing, nothing, about any restriction on identifiers.

+1.  The restriction on valid identifiers is very sensible (obviously,
since "m" needs to be accessible after "import m"), but a further
restriction seems just arbitrary.


More information about the Python-Dev mailing list