traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Re-word text

This commit is contained in:
Andrew M. Kuchling 2010-05-07 11:30:47 +00:00
parent d69e6ee656
commit d1e696b60f
1 changed files with 22 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
Doc/whatsnew/2.7.rst
View File

@ -69,8 +69,8 @@ The Future for Python 2.x
========================= =========================
Python 2.7 is intended to be the last major release in the 2.x series. Python 2.7 is intended to be the last major release in the 2.x series.
Though more major releases have not been absolutely ruled out, the The Python maintainers are planning to focus their future efforts on
Python maintainers are planning to focus their efforts on Python 3.x. the Python 3.x series.
This means that 2.7 will remain in place for a long time, running This means that 2.7 will remain in place for a long time, running
production systems that have not been ported to Python 3.x. production systems that have not been ported to Python 3.x.
@ -78,17 +78,27 @@ Two consequences of the long-term significance of 2.7 are:
* It's very likely the 2.7 release will have a longer period of * It's very likely the 2.7 release will have a longer period of
maintenance compared to earlier 2.x versions. Python 2.7 will maintenance compared to earlier 2.x versions. Python 2.7 will
continue to be maintained while the transition to 3.x is in continue to be maintained while the transition to 3.x continues.
progress, and that transition will itself be lengthy. Most 2.x Maintenance releases for Python 2.7 will probably be made for 5
versions are maintained for about 4 years, from the first to the years.
last bugfix release; patchlevel releases for Python 2.7 will
probably be made for at least 6 years.
* Because 2.7 will be running production applications, a policy * A policy decision was made to silence warnings only of interest to
decision was made to silence warnings only of interest to developers developers by default. :exc:`DeprecationWarning` and its
by default. Silencing :exc:`DeprecationWarning` and its descendants descendants are now ignored unless otherwise requested, preventing
prevents users from seeing warnings triggered by an application. users from seeing warnings triggered by an application. (Carried
(Carried out in :issue:`7319`.) out in :issue:`7319`.)
In previous releases, :exc:`DeprecationWarning` messages were
enabled by default, providing Python developers with a clear
indication of where their code may break in a future major version
of Python.
However, there are increasingly many users of Python-based
applications who are not directly involved in the development of
those applications. :exc:`DeprecationWarning` messages are
irrelevant to such users, making them worry about an application
that's actually working correctly and burdening the developers of
these applications with responding to these concerns.
You can re-enable display of :exc:`DeprecationWarning` messages by You can re-enable display of :exc:`DeprecationWarning` messages by
running Python with the :option:`-Wdefault` (short form: running Python with the :option:`-Wdefault` (short form: