RetroSearch Browse

Fri Sep 22 02:20:03 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-September/068911.html

On 9/21/06, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
> Giovanni Bajo wrote:
>
> > My idea (and interpretation of Greg's statement) is that a module/package
> > should be able to live with either relative imports within itself, or fully
> > absolute imports.
>
> I think it goes further than that -- each module should
> (potentially) have its own unique view of the module
> namespace, defined at the time the module is installed,
> that can't be disturbed by anything that any other module
> does.

Well, maybe. But there's also the requirement that if packages A and B
both import C, they should get the same C. Having multiple versions of
the same package loaded simultaneously sounds like a recipe for
disaster.

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)

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

Showing content from https://mail.python.org/pipermail/python-dev/2006-September/068911.html below:

[Python-Dev] New relative import issue