[Python-Dev] Alternative Approach to Relative Imports
Wed, 22 Sep 1999 12:25:25 -0400
Guido van Rossum wrote:
> > > Comment 2: I generally like this scheme, but think (for
> > > consistency and confusion-reduction) that it should go straight
> > > up the tree, instead of checking the root second.
> > That would probably break code because the search could
> > find some other module having the same name as a top-level
> > one. OTOH, perhaps that situation is not all the common to
> > fear too much about it.
> > Walking up all the way would certainly be easier to explain to
> > a 12-year old ;-)
> Yes, please. Do the long-term understandable thing here. I expect
> not too many packages have defined subpackages (or submodules) whose
> name conflicts with a standard library module, so you ought to be
> pretty safe here!
Walking straight up the tree is my preference. I think it is
Jim Fulton mailto:firstname.lastname@example.org Python Powered!
Technical Director (888) 344-4332 http://www.python.org
Digital Creations http://www.digicool.com http://www.zope.org
Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission. Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for