diff options
| author | Stéphane Wirtel <stephane@wirtel.be> | 2018-10-26 22:58:26 (GMT) |
|---|---|---|
| committer | Brett Cannon <brettcannon@users.noreply.github.com> | 2018-10-26 22:58:26 (GMT) |
| commit | 12e696b4f071ffe0d585b7f0d0d8020fd328bfdd (patch) | |
| tree | 81ff44e5896a18441710a3e8f24543bf4d9382f5 /Doc/whatsnew/3.3.rst | |
| parent | 9e14e49f13ef1a726f31efe6689285463332db6e (diff) | |
| download | cpython-12e696b4f071ffe0d585b7f0d0d8020fd328bfdd.zip cpython-12e696b4f071ffe0d585b7f0d0d8020fd328bfdd.tar.gz cpython-12e696b4f071ffe0d585b7f0d0d8020fd328bfdd.tar.bz2 | |
bpo-35042: Use the :pep: role where a PEP is specified (#10036)
Diffstat (limited to 'Doc/whatsnew/3.3.rst')
| -rw-r--r-- | Doc/whatsnew/3.3.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Doc/whatsnew/3.3.rst b/Doc/whatsnew/3.3.rst index 8862b37..ea03684 100644 --- a/Doc/whatsnew/3.3.rst +++ b/Doc/whatsnew/3.3.rst @@ -217,7 +217,7 @@ exist in parallel; over time, this compatibility should be phased out. On the Python side, there should be no downside to this change. -On the C API side, PEP 393 is fully backward compatible. The legacy API +On the C API side, :pep:`393` is fully backward compatible. The legacy API should remain available at least five years. Applications using the legacy API will not fully benefit of the memory reduction, or - worse - may use a bit more memory, because Python may have to maintain two versions of each @@ -2082,7 +2082,7 @@ Add a new :class:`types.MappingProxyType` class: Read-only proxy of a mapping. The new functions :func:`types.new_class` and :func:`types.prepare_class` provide support -for PEP 3115 compliant dynamic type creation. (:issue:`14588`) +for :pep:`3115` compliant dynamic type creation. (:issue:`14588`) unittest @@ -2396,7 +2396,7 @@ Porting Python code case of working with :term:`path entry finders <path entry finder>`. * :mod:`pkgutil` has been converted to use :mod:`importlib` internally. This - eliminates many edge cases where the old behaviour of the PEP 302 import + eliminates many edge cases where the old behaviour of the :pep:`302` import emulation failed to match the behaviour of the real import system. The import emulation itself is still present, but is now deprecated. The :func:`pkgutil.iter_importers` and :func:`pkgutil.walk_packages` functions @@ -2472,7 +2472,7 @@ Porting C code functions using this type are deprecated (but will stay available for at least five years). If you were using low-level Unicode APIs to construct and access unicode objects and you want to benefit of the - memory footprint reduction provided by PEP 393, you have to convert + memory footprint reduction provided by :pep:`393`, you have to convert your code to the new :doc:`Unicode API <../c-api/unicode>`. However, if you only have been using high-level functions such as |