[Python-Dev] Relative vs. absolute imports (original) (raw)

M.-A. Lemburg mal at egenix.com
Mon May 17 11:37:31 EDT 2004

Samuele Pedroni wrote:

At 16:55 17.05.2004 +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) if you pass globals = {} you get absolute imports from import,

Ahh, a hidden feature :-) I didn't know that one yet.

It is probably true that in the long run, given the new semantics, moving responsabilities away from/changing import contract could make sense.

-- Marc-Andre Lemburg eGenix.com

Professional Python Services directly from the Source (#1, May 17 2004)

Python/Zope Consulting and Support ... http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/

EuroPython 2004, Göteborg, Sweden 20 days left

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::

More information about the Python-Dev mailing list