From 3ebff0a2a8c905617597c0f2166743801a1a5bf7 Mon Sep 17 00:00:00 2001 From: Paul Caprioli Date: Fri, 27 Feb 2026 16:51:35 -0800 Subject: [PATCH] PEP 803: fix minor typos --- peps/pep-0803.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/peps/pep-0803.rst b/peps/pep-0803.rst index d8641170131..9d78a348bc4 100644 --- a/peps/pep-0803.rst +++ b/peps/pep-0803.rst @@ -58,7 +58,7 @@ Python's Stable ABI (``abi3`` for short), as defined in :pep:`384` and :pep:`652`, provides a way to compile extension modules that can be loaded on multiple minor versions of the CPython interpreter. Several projects use this to limit the number of -:ref:`wheels ` (binary artefacts) +:ref:`wheels ` (binary artifacts) that need to be built and distributed for each release, and/or to make it easier to test with pre-release versions of Python. @@ -311,7 +311,7 @@ We will strive to keep it as a subset, but will not guarantee this. Since ``abi3t`` and ``abi3`` will overlap, it will be possible for a single compiled extension to support both at once, and thus be compatible with -CPython 3.15+ (both free-threaded and GIL-eanbled builds). +CPython 3.15+ (both free-threaded and GIL-enabled builds). Initially, any extension compiled for ``abi3t`` will be compatible with ``abi3`` as well. @@ -350,7 +350,7 @@ set the configuration macros automatically in the following situations: Opaque PyObject --------------- -``abi3t`` will initially have a single diffenerce from ``abi3``: the +``abi3t`` will initially have a single difference from ``abi3``: the ``PyObject`` structure and APIs that depend on it are not part of ``abi3t``. Specifically, when building for ``abi3t``, the CPython headers will: @@ -371,7 +371,7 @@ Specifically, when building for ``abi3t``, the CPython headers will: - :c:macro:`PyObject_VAR_HEAD` - :c:func:`Py_SET_TYPE` -In both the regular stable ABI (``abit3`` 3.15+) and the new +In both the regular stable ABI (``abi3`` 3.15+) and the new ``abi3t``, the following will be exported functions (exposed in the ABI) rather than macros: @@ -474,7 +474,7 @@ Recommendations for installers Package installers should treat this tag as completely separate from ``abi3``. They should allow ``abi3t``-tagged wheels for free-threaded builds wherever -they currently allow ``abi3``-tagged ones for (orherwise equal) +they currently allow ``abi3``-tagged ones for (otherwise equal) non-free-threaded builds. Recommendations for build tools