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

[Python-Dev] Import and unicode: part two

[Python-Dev] Import and unicode: part two [Python-Dev] Import and unicode: part twoBrett Cannon brett at python.org
Wed Jan 19 19:23:02 CET 2011
On Wed, Jan 19, 2011 at 07:01, Simon Cross
<hodgestar+pythondev at gmail.com> wrote:
> On Wed, Jan 19, 2011 at 2:34 PM, Victor Stinner
> <victor.stinner at haypocalc.com> wrote:
>>  (a) Python 3 doesn't support non-ASCII module names
>
> -0: I'm vaguely against this being supported because I'd rather not
> have to deal with what happens when the guess regarding the filesystem
> encoding is wrong. On the other hand, a general encouragement to stick
> to ASCII module names is probably functionally equivalent without
> imposing a hard restriction.

-0 from me (unless the Unicode variable naming PEP says otherwise).

>
>>  (b) Python 3 doesn't support unencodable characters in the module path
>
> +1: It'd be nice if Python could import modules regardless of what
> folder names people happen to have on their module path.

+1 from me as well (nervously hoping importlib already supports it  =) .
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