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

[Python-Dev] Import and unicode: part two

[Python-Dev] Import and unicode: part two [Python-Dev] Import and unicode: part twoVictor Stinner victor.stinner at haypocalc.com
Wed Jan 19 22:10:35 CET 2011
Le mercredi 19 janvier 2011 à 13:38 -0500, Alexander Belopolsky a
écrit :
> PEP 3131 does not distinguish between different types of identifiers,
> so I think it assumes that non-ascii module names should be supported.

My opinion is that we should suport non-ASCII module names and
unencodable paths if it doesn't introduce an overhead (make Python
slower and add a lot of code). My patch adds ~400 lines of code (I think
that it is small: the patch adds many functions), but I think that it
makes Python as fast, or maybe faster.

Victor

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