From: R David Murray Date: Mon, 23 Dec 2013 02:05:04 +0000 (-0500) Subject: Make mailing list thread reference an inline link, reword i.e. abbreviation. X-Git-Tag: v3.4.0b2~123 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=e9b74d45d3262258fd214fc0a664cab2ebd7efa5;p=thirdparty%2FPython%2Fcpython.git Make mailing list thread reference an inline link, reword i.e. abbreviation. --- diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst index f43e441431aa..616de2d4364f 100644 --- a/Doc/whatsnew/3.4.rst +++ b/Doc/whatsnew/3.4.rst @@ -97,7 +97,7 @@ New expected features for Python implementations: * :ref:`improvements ` in the handling of codecs that are not text encodings * :ref:`A ModuleSpec Type ` for the Import System - (:pep:`451`). + (:pep:`451`). (Affects importer authors.) New library modules: @@ -283,12 +283,12 @@ PEP 451: A ModuleSpec Type for the Import System ------------------------------------------------ :pep:`451` provides an encapsulation of the information about a module -that the import machinery will use to load it, (i.e. a module spec). +that the import machinery will use to load it (that is, a module specification). This helps simplify both the import implementation and several -import-related APIs. The change is also a stepping stone for several -future import-related improvements. +import-related APIs. The change is also a stepping stone for `several +future import-related improvements`__. -https://mail.python.org/pipermail/python-dev/2013-November/130111.html +__ https://mail.python.org/pipermail/python-dev/2013-November/130111.html The public-facing changes from the PEP are entirely backward-compatible. Furthermore, they should be transparent to everyone but importer