Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #66449
| References | <roy-34FC23.10062115022014@news.panix.com> |
|---|---|
| Date | 2014-02-16 02:26 +1100 |
| Subject | Re: Absolute imports? |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.7004.1392477977.18130.python-list@python.org> (permalink) |
On Sun, Feb 16, 2014 at 2:06 AM, Roy Smith <roy@panix.com> wrote: > It also says, "This absolute-import behaviour will become the default in > a future version (probably Python 2.7)", but it appears that 2.7.6 is > still doing relative by default. > Since absolute imports can be controlled with a future directive, you can check it out via that module: >>> import __future__ >>> __future__.absolute_import _Feature((2, 5, 0, 'alpha', 1), (3, 0, 0, 'alpha', 0), 16384) Looks like it was held over for 3.0 rather than potentially breaking stuff across 2.6->2.7. ChrisA
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Absolute imports? Roy Smith <roy@panix.com> - 2014-02-15 10:06 -0500 Re: Absolute imports? Chris Angelico <rosuav@gmail.com> - 2014-02-16 02:26 +1100 Re: Absolute imports? Peter Otten <__peter__@web.de> - 2014-02-15 16:46 +0100
csiph-web