RetroSearch Browse

Mon Apr 5 13:58:21 EDT 2004 · http://mail.python.org/pipermail/python-dev/2004-April/044082.html

> > 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.

I think we ought to start it as a normal Deprecation.  If there are
enough people who get bit by it during alpha testing we can switch it
to PendingDeprecation, but IMO PendingDeprecation is not very useful
(since it is ignored by default).

--Guido van Rossum (home page: http://www.python.org/~guido/)

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

Showing content from http://mail.python.org/pipermail/python-dev/2004-April/044082.html below:

[Python-Dev] Re: PEP 328 -- relative and multi-line import