A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-July/112301.html below:

[Python-Dev] status of absolute_import w/ python 2.7

[Python-Dev] status of absolute_import w/ python 2.7 [Python-Dev] status of absolute_import w/ python 2.7Éric Araujo merwok at netwok.org
Wed Jul 13 16:34:54 CEST 2011
Le 13/07/2011 06:40, Nick Coghlan a écrit :
> Now, the what's new for 2.7 doesn't actually *say* we made that change
> and I can't find any evidence for it in NEWS either, so I think the
> bug is actually in the __future__ module (and docs:
> http://docs.python.org/library/__future__).

I seemed to recall the change was done in 2.6, but I found only that:

> C API: the PyImport_Import() and PyImport_ImportModule() functions
> now default to absolute imports, not relative imports. This will
> affect C extensions that import other modules.

http://docs.python.org/dev/whatsnew/2.6#porting-to-python-2-6

Regards
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4