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/107573.html below:

[Python-Dev] Import and unicode: part two

[Python-Dev] Import and unicode: part two [Python-Dev] Import and unicode: part twoStephen J. Turnbull stephen at xemacs.org
Fri Jan 21 11:42:14 CET 2011
Atsuo Ishimoto writes:

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

So why wouldn't Python work the same way?  The rest of the world can
use non-ASCII modules names sparingly, and Japanese programmers can
avoid them diligently.  Or learn to use them properly and teach each
other; if anybody has the experience of multiple encodings needed to
figure out a good way to use the native language in program
identifiers despite the encoding problem, my bet is it would be Japan.


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