Re: Forcing absolute package imports in 2.7?

From	aahz@pythoncraft.com (Aahz)
Newsgroups	comp.lang.python
Subject	Re: Forcing absolute package imports in 2.7?
Date	2011-04-13 16:10 -0700
Organization	The Cat & Dragon
Message-ID	<io5age$l2s$1@panix5.panix.com> (permalink)
References	<mailman.23.1301538403.2990.python-list@python.org>

Show all headers | View raw

In article <mailman.23.1301538403.2990.python-list@python.org>,
Michael Parker  <michael.g.parker@gmail.com> wrote:
>
>I'm reading Learning Python 4th Edition by Lutz. In the section on
>relative package imports, he says: "In Python 3.0, the `import
>modname` statement is always absolute, skipping the containing
>package=92s directory. In 2.6, this statement form still performs
>relative imports today (i.e., the package=92s directory is searched
>first), but these will become absolute in Python 2.7, too.`
>
>But in my own testing I'm not seeing this behavior. Was it not
>included in 2.7 for fear of breaking too many programs?

from __future__ import absolute_import   
-- 
Aahz (aahz@pythoncraft.com)           <*>         http://www.pythoncraft.com/

"At Resolver we've found it useful to short-circuit any doubt and just        
refer to comments in code as 'lies'. :-)"
--Michael Foord paraphrases Christian Muirhead on python-dev, 2009-03-22

Back to comp.lang.python | Previous | Next | Find similar

Thread

Re: Forcing absolute package imports in 2.7? aahz@pythoncraft.com (Aahz) - 2011-04-13 16:10 -0700

csiph-web