Skip to content

PEP 803: fix minor typos #4835

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hpkfft wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −5
Open

PEP 803: fix minor typos #4835

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions peps/pep-0803.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <packaging:binary-distribution-format>` (binary artefacts)
:ref:`wheels <packaging:binary-distribution-format>` (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.

Expand Down Expand Up @@ -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.

Expand Down Expand Up @@ -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:
Expand All @@ -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:

Expand Down Expand Up @@ -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
Expand Down
Loading