RetroSearch Browse

Wed Jan 19 22:05:41 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-January/107495.html

On Wed, Jan 19, 2011 at 10:32 PM, Terry Reedy <tjreedy at udel.edu> wrote:
> 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.

I have no problem with non-ASCII module identifiers being valid
syntax. It's a question of whether attempting to translate a non-ASCII
module name into a file name (so the file can be imported) is a good
idea and whether these sorts of files can be safely transferred among
diverse filesystems.

For similar reasons we tend to avoid capital letters in module names.

Schiavo
Simon

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-January/107495.html below:

[Python-Dev] Import and unicode: part two