A RetroSearch Logo

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

Search Query:

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

[Python-Dev] Import and unicode: part two

[Python-Dev] Import and unicode: part two [Python-Dev] Import and unicode: part twoTerry Reedy tjreedy at udel.edu
Wed Jan 19 22:40:24 CET 2011
On 1/19/2011 4:05 PM, Simon Cross wrote:

> I have no problem with non-ASCII module identifiers being valid
> syntax. It's a question of whether attempting to translate a non-ASCII

If the names are the same, ie, produced with the same sequence of 
keystrokes in the save-as box and importing box, then there is no 
translation, at least from the user's view.

> 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.

I believe we now have the situation that a package that works on *nix 
could fail on Windows, whereas I believe that patch would *improve* 
portability.

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

That is a stdlib style guide followed by many, but intentionally not 
enforced.


-- 
Terry Jan Reedy

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4