[Python-checkins] (no subject)

Thu Sep 26 03:06:49 EDT 2019

To: python-checkins at python.org
Subject: Doc: Several fixes and improvements for 3.9 whatsnew (GH-16375)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

https://github.com/python/cpython/commit/6a10d59541f8ec9fa548e012d4595b39d141=
e1cc
commit: 6a10d59541f8ec9fa548e012d4595b39d141e1cc
branch: master
author: Kyle Stanley <aeros167 at gmail.com>
committer: St=C3=A9phane Wirtel <stephane at wirtel.be>
date: 2019-09-26T09:06:46+02:00
summary:

Doc: Several fixes and improvements for 3.9 whatsnew (GH-16375)

files:
M Doc/whatsnew/3.9.rst

diff --git a/Doc/whatsnew/3.9.rst b/Doc/whatsnew/3.9.rst
index 200d9627ca52..690b536fd881 100644
--- a/Doc/whatsnew/3.9.rst
+++ b/Doc/whatsnew/3.9.rst
@@ -75,27 +75,27 @@ New Features
 Other Language Changes
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=20
-* :func:`builtins.__import__` now raises :exc:`ImportError` instead of
-  :exc:`ValueError` as used to occur when a relative import went past
+* :func:`__import__` now raises :exc:`ImportError` instead of
+  :exc:`ValueError`, which used to occur when a relative import went past
   its top-level package.
   (Contributed by Ngalim Siregar in :issue:`37444`.)
=20
=20
 * Python now gets the absolute path of the script filename specified on
   the command line (ex: ``python3 script.py``): the ``__file__`` attribute of
-  the ``__main__`` module, ``sys.argv[0]`` and ``sys.path[0]`` become an
+  the :mod:`__main__` module, ``sys.argv[0]`` and ``sys.path[0]`` become an
   absolute path, rather than a relative path. These paths now remain valid
   after the current directory is changed by :func:`os.chdir`. As a side effe=
ct,
-  a traceback also displays the absolute path for ``__main__`` module frames=
 in
-  this case.
+  a traceback also displays the absolute path for :mod:`__main__` module fra=
mes
+  in this case.
   (Contributed by Victor Stinner in :issue:`20443`.)
=20
 * In development mode and in debug build, *encoding* and *errors* arguments =
are
   now checked on string encoding and decoding operations. Examples:
   :func:`open`, :meth:`str.encode` and :meth:`bytes.decode`.
=20
-  By default, for best performances, the *errors* argument is only checked at
-  the first encoding/decoding error, and the *encoding* argument is sometimes
+  By default, for best performance, the *errors* argument is only checked at
+  the first encoding/decoding error and the *encoding* argument is sometimes
   ignored for empty strings.
   (Contributed by Victor Stinner in :issue:`37388`.)
=20
@@ -119,15 +119,16 @@ multiline indented output.
 asyncio
 -------
=20
-Added a new couroutine :meth:`loop.shutdown_default_executor` that schedules
-a shutdown for the default executor that waits on the threadpool to finish
-closing. Also, :func:`asyncio.run` has been updated to use the new coroutine.
+Added a new :term:`coroutine` :meth:`~asyncio.loop.shutdown_default_executor`
+that schedules a shutdown for the default executor that waits on the
+:class:`~concurrent.futures.ThreadPoolExecutor` to finish closing. Also,
+:func:`asyncio.run` has been updated to use the new :term:`coroutine`.
 (Contributed by Kyle Stanley in :issue:`34037`.)
=20
 threading
 ---------
=20
-In a subinterpreter, spawning a daemon thread now raises an exception. Daemon
+In a subinterpreter, spawning a daemon thread now raises a :exc:`RuntimeErro=
r`. Daemon
 threads were never supported in subinterpreters. Previously, the subinterpre=
ter
 finalization crashed with a Python fatal error if a daemon thread was still
 running.
@@ -164,8 +165,8 @@ Optimizations
 Build and C API Changes
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=20
-* Add a new public :c:func:`PyObject_CallNoArgs` function to the C API:
-  call a callable Python object without any arguments. It is the most effici=
ent
+* Add a new public :c:func:`PyObject_CallNoArgs` function to the C API, which
+  calls a callable Python object without any arguments. It is the most effic=
ient
   way to call a callable Python object without any argument.
   (Contributed by Victor Stinner in :issue:`37194`.)
=20
@@ -176,18 +177,18 @@ Deprecated
=20
 * Currently :func:`math.factorial` accepts :class:`float` instances with
   non-negative integer values (like ``5.0``).  It raises a :exc:`ValueError`
-  for non-integral and negative floats.  It is deprecated now.  In future
+  for non-integral and negative floats.  It is now deprecated.  In future
   Python versions it will raise a :exc:`TypeError` for all floats.
   (Contributed by Serhiy Storchaka in :issue:`37315`.)
=20
 * The :mod:`parser` module is deprecated and will be removed in future versi=
ons
-  of Python. For the majority of use cases users can leverage the Abstract S=
yntax
+  of Python. For the majority of use cases, users can leverage the Abstract =
Syntax
   Tree (AST) generation and compilation stage, using the :mod:`ast` module.
=20
 * The :mod:`random` module currently accepts any hashable type as a
   possible seed value.  Unfortunately, some of those types are not
   guaranteed to have a deterministic hash value.  After Python 3.9,
-  the module will restrict its seeds to *None*, :class:`int`,
+  the module will restrict its seeds to :const:`None`, :class:`int`,
   :class:`float`, :class:`str`, :class:`bytes`, and :class:`bytearray`.
=20
=20
@@ -195,7 +196,7 @@ Removed
 =3D=3D=3D=3D=3D=3D=3D
=20
 * The undocumented ``sys.callstats()`` function has been removed. Since Pyth=
on
-  3.7, it was deprecated and always returned ``None``. It required a special
+  3.7, it was deprecated and always returned :const:`None`. It required a sp=
ecial
   build option ``CALL_PROFILE`` which was already removed in Python 3.7.
   (Contributed by Victor Stinner in :issue:`37414`.)
=20
@@ -213,7 +214,7 @@ Removed
   (Contributed by Victor Stinner in :issue:`37312`.)
=20
 * ``aifc.openfp()`` alias to ``aifc.open()``, ``sunau.openfp()`` alias to
-  ``sunau.open()``, and ``wave.openfp()`` alias to ``wave.open()`` have been
+  ``sunau.open()``, and ``wave.openfp()`` alias to :func:`wave.open()` have =
been
   removed. They were deprecated since Python 3.7.
   (Contributed by Victor Stinner in :issue:`37320`.)
=20
@@ -229,16 +230,16 @@ Removed
   (Contributed by Serhiy Storchaka in :issue:`36543`.)
=20
 * The old :mod:`plistlib` API has been removed, it was deprecated since Pyth=
on
-  3.4. Use the :func:`load`, :func:`loads`, :func:`dump`, and :func:`dumps`
-  functions. Additionally, the ``use_builtin_types`` parameter was removed,
-  standard :class:`bytes` objects are always used.
+  3.4. Use the :func:`~plistlib.load`, :func:`~plistlib.loads`, :func:`~plis=
tlib.dump`, and
+  :func:`~plistlib.dumps` functions. Additionally, the *use_builtin_types* p=
arameter was
+  removed, standard :class:`bytes` objects are always used instead.
   (Contributed by Jon Janzen in :issue:`36409`.)
=20
-* ``PyThreadState_DeleteCurrent()`` has been removed. It was not documented.
+* The C function ``PyThreadState_DeleteCurrent()`` has been removed. It was =
not documented.
   (Contributed by Joannah Nanjekye in :issue:`37878`.)
=20
 * The C function ``PyGen_NeedsFinalizing`` has been removed. It was not
-  documented, tested or used anywhere within CPython after the implementation
+  documented, tested, or used anywhere within CPython after the implementati=
on
   of :pep:`442`. Patch by Joannah Nanjekye.
   (Contributed by Joannah Nanjekye in :issue:`15088`)
=20
@@ -253,11 +254,10 @@ that may require changes to your code.
 Changes in the Python API
 -------------------------
=20
-* :func:`builtins.__import__` and :func:`importlib.util.resolve_name` now ra=
ise
+* :func:`__import__` and :func:`importlib.util.resolve_name` now raise
   :exc:`ImportError` where it previously raised :exc:`ValueError`. Callers
   catching the specific exception type and supporting both Python 3.9 and
-  earlier versions will need to catch both:
-  ``except (ImportError, ValueError):``
+  earlier versions will need to catch both using ``except (ImportError, Valu=
eError):``.
=20
 * The :mod:`venv` activation scripts no longer special-case when
   ``__VENV_PROMPT__`` is set to ``""``.

