Skip to content
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

Jump to bottom

PEP 656: Minor clarification on relation to PEP 600 #1911

Merged
merged 2 commits into from Apr 5, 2021
Merged

PEP 656: Minor clarification on relation to PEP 600 #1911

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
07cec7f
Minor clarification on relation to PEP 600
uranusjr Apr 5, 2021
e0f16fb
Also expand on the tag definition on dependency
uranusjr Apr 5, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
19 changes: 16 additions & 3 deletions pep-0656.rst
View file
Open in desktop
Expand Up @@ -42,9 +42,10 @@ run against a newer musl runtime [musl-compat-ml]_. Therefore, we use
a scheme similar to the glibc-version-based manylinux tags, but
against musl versions instead of glibc.

Logic behind the new platform tag largely follows :pep:`600`, and
require wheels using this tag make similar promises. Please refer to
the PEP for more details on rationale and reasoning behind the design.
Logic behind the new platform tag largely follows :pep:`600`
("perennial manylinux"), and requires wheels using this tag make
similar promises. Please refer to :pep:`600` for more details on
rationale and reasoning behind the design.

The ``musllinux`` platform tags only apply to Python interpreters
dynamically linked against the musl libc and executed on the runtime
Expand All @@ -62,6 +63,18 @@ Tags using the new scheme will take the form::

musllinux_${MUSLMAJOR}_${MUSLMINOR}_${ARCH}

This tag promises the wheel works on any mainstream Linux distribution
that uses musl version ``${MUSLMAJOR}.${MUSLMINOR}``, following the
perennial design. All other system-level dependency requirements rely
on the community's definition to the intentionally vague "mainstream"
description introduced in :pep:`600`. A wheel may make use of newer
system dependencies when all mainstream distributions using the
specified musl version provide the dependency by default; once all
mainstream distributions on the musl version ship a certain dependency
version by default, users relying on older versions are automatically
removed from the coverage of that ``musllinux`` tag.


Reading the musl version
------------------------

Expand Down