Add a note that deprecations in 2.9 are optional since they might not be
desirable considering how many changes between 2.9 and 3.0 there will be and thus deprecating everything could make 2.9 rather "noisy" in terms of deprecations.
This commit is contained in:
parent
99ef26d876
commit
bf5ba1dd1c
11
pep-0352.txt
11
pep-0352.txt
|
@ -189,6 +189,15 @@ semantics starting in the version following the introduction of the
|
||||||
deprecation and the raising of a DeprecationWarning for the version
|
deprecation and the raising of a DeprecationWarning for the version
|
||||||
specifically listed.
|
specifically listed.
|
||||||
|
|
||||||
|
Deprecation of features in Python 2.9 is optional. This is because it
|
||||||
|
is not known at this time if Python 2.9 (which is slated to be the last version
|
||||||
|
in the 2.x series) will actively deprecate features that will not be in 3.0 .
|
||||||
|
It is conceivable that no deprecation warnings will be used in 2.9 since
|
||||||
|
there could be such a difference between 2.9 and 3.0 that it would make 2.9 too
|
||||||
|
"noisy" in terms of warnings. Thus the proposed deprecation warnings for
|
||||||
|
Python 2.9 will be revisited when development of that version begins to
|
||||||
|
determine if they are still desired.
|
||||||
|
|
||||||
* Python 2.5
|
* Python 2.5
|
||||||
|
|
||||||
- introduce BaseException
|
- introduce BaseException
|
||||||
|
@ -215,7 +224,7 @@ specifically listed.
|
||||||
|
|
||||||
* Python 2.9
|
* Python 2.9
|
||||||
|
|
||||||
- deprecate ``args`` and ``__getitem__``
|
- deprecate ``args`` and ``__getitem__`` (optional)
|
||||||
|
|
||||||
* Python 3.0
|
* Python 3.0
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue