On Mon, Apr 05, 2004, Bernhard Herzog wrote: > Aahz <aahz at pythoncraft.com> writes: >> >> You may use relative imports freely. In Python 2.5, any ``import`` >> statement that results in an intra-package import will generate a >> ``PendingDeprecation`` warning (this also applies to ``from <> import`` >> that fails to use the relative import syntax). In Python 2.6, ``import`` >> will always be an absolute import. > > Why PendingDeprecation? If the import semantics change in incompatible > ways in 2.6, 2.5 should generate a "normal" DeprecationWarning, I think. Guido can overrule this, but my take is that there will be few enough cases where this is a significant issue. People who want to write cross-version libraries and applications shouldn't have to deal with suppressing the DeprecationWarning. If we were serious about issuing a DeprecationWarning, I think that would need to be in Python 2.6, pushing the default of absolute imports to Python 2.7. That seems too long a timeline to me. Other opinions? -- Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/ Why is this newsgroup different from all other newsgroups?
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