[Python-Dev] Re: PEP 328 -- relative and multi-line import (original) (raw)
Aahz aahz at pythoncraft.com
Sat Apr 3 21🔞00 EST 2004
- Previous message: [Python-Dev] Re: PEP 328 -- relative and multi-line import
- Next message: [Python-Dev] Re: PEP 328 -- relative and multi-line import
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Apr 03, 2004, Guido van Rossum wrote:
Aahz:
(I think the PEP makes that clear). You could, however, do from ... import package [as foo] if Guido permits it; I want a Pronouncement on that before adding it to the PEP. Yes, even if ... refers to the root package (but not if it tries to reach beyond that).
Great! Then PEP 328 is almost set except for Bernhard's wish for more clarification of the rationale for making the default import absolute. I've gone ahead and updated the PEP, and I think we should move forward on implementation even without the clarification, but I've stuck a note in my calendar to bug people regularly until the rationale is finished.
I've added the following:
Timeline
In Python 2.4, you must enable the new absolute import behavior with ::
from __future__ import absolute_import
You may use relative imports freely. In Python 2.5, any import
statement that results in an intra-package import will generate a
PendingDeprecation
warning (this also applies to from <> import
that fails to use the relative import syntax). In Python 2.6, import
will always be an absolute import.
Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/
"usenet imitates usenet" --Darkhawk
- Previous message: [Python-Dev] Re: PEP 328 -- relative and multi-line import
- Next message: [Python-Dev] Re: PEP 328 -- relative and multi-line import
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]