[Python-Dev] Import and unicode: part two

Alexander Belopolsky alexander.belopolsky at gmail.com
Thu Jan 20 06:15:03 CET 2011

On Wed, Jan 19, 2011 at 11:39 PM, Toshio Kuratomi <a.badger at gmail.com> wrote:
> Teaching students to write non-portable code (relying on filesystem encoding
> where your solution is, don't upload to pypi anything that has non-ascii
> filenames) seems like the exact opposite of how you'd want to shape a young
> student's understanding of good programming practices.

Let's not confuse language definition with the quality of
implementation.   It would be a perfectly valid Python implementation
that would run on a system that does not even have a traditional
filesystem and "import foo" looks up foo module code in an in-memory
database.   Should Python be redefined so that module names are case
insensitive simply because case insensitive filesystems are still
popular?  I don't think so.

More information about the Python-Dev mailing list