A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2004-May/044860.html below:

[Python-Dev] Relative vs. absolute imports

[Python-Dev] Relative vs. absolute imports [Python-Dev] Relative vs. absolute importsPhillip J. Eby pje at telecommunity.com
Mon May 17 11:04:15 EDT 2004
At 04:55 PM 5/17/04 +0200, M.-A. Lemburg wrote:
>Phillip J. Eby wrote:
>>At 03:42 PM 5/17/04 +0200, M.-A. Lemburg wrote:
>>
>>>I have a few questions about the PEP 328 which I'd like discussed:
>>>
>>>* Why do we absolutely need to change the current scheme
>>>   of 'local, then absolute' for name resolution ?
>>Because there's no way to override the current scheme without calling 
>>__import__ directly.
>
>Are you saying that you are not going to change the default __import__()
>implementation, only the way it is called ? (I wonder how you'll
>enforce the 'absolute only' strategy then)

Huh?  You lost me.  What 'absolute only'?  There's "from .x import y" 
still, and that's relative.

As far as I know, nothing about __import__ is changing, only the spelling 
of import statements.


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