Record that old names won't be deprecated
This commit is contained in:
parent
32804645ab
commit
84dda3bb67
11
pep-3151.txt
11
pep-3151.txt
|
@ -276,8 +276,9 @@ by Python code.
|
|||
Deprecation of names
|
||||
--------------------
|
||||
|
||||
It is not yet decided whether the old names will be deprecated (then removed)
|
||||
or all names will continue living forever in the builtins namespace.
|
||||
The following paragraphs outline a possible deprecation strategy for
|
||||
old exception names. However, it has been decided to keep them as aliases
|
||||
for the time being. This decision could be revised in time for Python 4.0.
|
||||
|
||||
built-in exceptions
|
||||
'''''''''''''''''''
|
||||
|
@ -497,10 +498,8 @@ Implementation
|
|||
A reference implementation is available in
|
||||
http://hg.python.org/features/pep-3151/ in branch ``pep-3151``. It is
|
||||
also tracked on the bug tracker at http://bugs.python.org/issue12555.
|
||||
Its current state is that all semantic changes and additions are implemented,
|
||||
but the `deprecation of names`_ mechanism isn't. It has been successfully
|
||||
tested on a variety of systems: Linux, Windows, OpenIndiana and FreeBSD
|
||||
buildbots.
|
||||
It has been successfully tested on a variety of systems: Linux, Windows,
|
||||
OpenIndiana and FreeBSD buildbots.
|
||||
|
||||
One source of trouble has been with the respective constructors of ``IOError``
|
||||
and ``WindowsError``, which were incompatible. The way it is solved is by
|
||||
|
|
Loading…
Reference in New Issue