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

PEP 620: Fix typos spotted by Terry Reedy

This commit is contained in:
Victor Stinner 2020-06-22 18:17:18 +02:00
parent bdf57430df
commit b42dae697f
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
pep-0620.rst
View File

@ -218,7 +218,7 @@ Header files must be reorganized in 3 API:
* ``Include/cpython/`` directory is the CPython C API: less "portable"
API, depends more on the Python version, expose some implementation
details, few incompatible changes can happen.
* ``Internal/internal/`` directory is the internal C API: implementation
* ``Include/internal/`` directory is the internal C API: implementation
details, incompatible changes are likely at each Python release.
The creation of the ``Include/cpython/`` directory is fully backward
@ -276,8 +276,8 @@ Private functions moved to the internal C API in Python 3.9:
* ``_PyDebug_PrintTotalRefs()``, ``_Py_PrintReferences()``,
``_Py_PrintReferenceAddresses()`` (not exported)
Public "clear free list" functions moved to the internal C API an
renamed to private functions and in Python 3.9:
Public "clear free list" functions moved to the internal C API and
renamed to private functions in Python 3.9:
* ``PyAsyncGen_ClearFreeLists()``
* ``PyContext_ClearFreeList()``
@ -297,7 +297,7 @@ renamed to private functions and in Python 3.9:
Convert macros to static inline functions
-----------------------------------------
Converting macros to static inline functions have multiple advantages:
Converting macros to static inline functions has multiple advantages:
* Functions have well defined parameter types and return type.
* Functions can use variables with a well defined scope (the function).
@ -308,7 +308,7 @@ Converting macros to static inline functions have multiple advantages:
<https://gcc.gnu.org/onlinedocs/cpp/Macro-Pitfalls.html>`_.
Converting macros to static inline functions should only impact very few
C extensions which use macros in unusual ways.
C extensions that use macros in unusual ways.
For backward compatibility, functions must continue to accept any type,
not only ``PyObject*``, to avoid compiler warnings, since most macros
@ -452,7 +452,7 @@ problem is to decide when it is safe to delete the temporary object.
The general guidelines is to avoid returning borrowed references for new
C API functions.
No function returning borrowed functions is scheduled for removal by
No function returning borrowed references is scheduled for removal by
this PEP.
**STATUS**: Completed (in Python 3.9)