RetroSearch Browse

Tue Jul 10 11:28:19 CEST 2007 · http://mail.python.org/pipermail/python-dev/2007-July/073807.html

Brett Cannon wrote:
> On 7/9/07, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> Given the above limitations, I propose that we document the new
>> attribute as follows:
>>
>> "If the module global __package__ exists when executing an import
>> statement, it is used to determine the base for relative imports,
>> instead of the __name__ and __path__ attributes.
> 
> That's fine.  __path__ actually isn't used to resolve relative imports
> into absolute ones anyway; it's used only as a substitute to sys.path
> when importing within a package.

I was referring to the fact that if __path__ is present (indicating a 
package), then the relative import is based directly on __name__, 
otherwise it is based on __name__.rpartition('.')[0].

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
---------------------------------------------------------------
             http://www.boredomandlaziness.org

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

Showing content from http://mail.python.org/pipermail/python-dev/2007-July/073807.html below:

[Python-Dev] PEP 366 - Relative imports from main modules