iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 606: minor edits

This commit is contained in:
Victor Stinner 2019-10-25 15:40:39 +02:00
parent 18b9fa51c1
commit 3a343027ca
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
pep-0606.rst
View File

@ -136,8 +136,8 @@ One of the `Zen of Python (PEP 20)
When Python evolves, new ways emerge inevitably. ``DeprecationWarning``
are emitted to suggest to use the new way, but many developers ignore
these warnings, which are silent by default (except in the ``__main__``
module: see the `PEP 565 <https://www.python.org/dev/peps/pep-0565/>_`).
Some developers simply ignore all warnings since they are too many
module: see the `PEP 565 <https://www.python.org/dev/peps/pep-0565/>`_).
Some developers simply ignore all warnings when there are too many
warnings, and so only bother with exceptions when deprecated code is
removed.
@ -148,14 +148,14 @@ change is backward incompatible.
Some developers can take the end of the Python 2 support as an
opportunity to push even more incompatible changes than usual.
Adding backward compatibility as an opt-in prevents to break
Adding an opt-in backward compatibility prevents to break
applications and allows developers to continue to do such cleanup.
Redistribute the maintenance burden
-----------------------------------
The backward compatibility involves authors of backward incompatible
The backward compatibility involves authors of incompatible
changes more in the upgrade path.
@ -205,16 +205,16 @@ compatibility is requested::
Deprecated open() "U" mode
--------------------------
The "U" mode of ``open()`` is deprecated since Python 3.4 and emits a
The ``"U"`` mode of ``open()`` is deprecated since Python 3.4 and emits a
``DeprecationWarning``. The `bpo-37330
<https://bugs.python.org/issue37330>`_ proposes to drop this mode:
``open()`` would raise an exception if ``U`` mode is used.
``open(filename, "rU")`` would raise an exception.
This change falls into the "cleanup" category: it is not required to
implement a feature.
A backward compatibility mode would be trivial to implement and would be
welcomed here by users.
welcomed by users.
Specification
@ -306,10 +306,10 @@ Alternatives
Provide a workaround for each incompatible change
-------------------------------------------------
An application can works around most of the incompatible changes which
An application can work around most incompatible changes which
impacts it.
For example, ``collections`` aliases can be added again using::
For example, ``collections`` aliases can be added back using::
import collections.abc
collections.Mapping = collections.abc.Mapping