[Python-Dev] Import and unicode: part two

Atsuo Ishimoto ishimoto at gembook.org
Fri Jan 21 07:44:43 CET 2011

On Fri, Jan 21, 2011 at 2:59 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> These all sound like good reasons to continue to *advise* against
> using non-ASCII module names. But aside from that, they sound exactly
> like a lot of the arguments we heard when Py3k started enforcing the
> bytes/text distinction more rigorously: "you're going to break
> stuff!".

No, non-ASCII module names are new breakage you are going to introduce now :)
If the advice against using non-ASCII module names is reasonable, why
bother supporting them?

> Yes, we know. But if core software development components like Python
> don't try to improve their Unicode support, how is the situation ever
> going to get better?

Java, a leading language of IT industry, have already support
non-ASCII class files for years. But I've never seen such files in
production in Japan, and didn't improve situation until now.

Atsuo Ishimoto
Mail: ishimoto at gembook.org
Blog: http://d.hatena.ne.jp/atsuoishimoto/
Twitter: atsuoishimoto

More information about the Python-Dev mailing list