PEP 825: Collected updates - #5110
Open
konstin wants to merge 23 commits into
Open
Conversation
Add peps/pep-0825/appendix-metadata-consistency.rst, setting out why the metadata consistency requirements are justified, what they cost, and what they deliberately leave open. It covers the 2024 "Enforcing consistent metadata" DPO thread and the status of its two prominent cases, the resolver cost that forced dependency divergence would impose, and why divergent variant metadata specifically is incoherent rather than expressive. It includes a survey of which build backends can emit `Dynamic: Requires-Dist` in wheel METADATA, which establishes that the alternative to variant environment markers is reachable today only through `setuptools` with a `setup.py`. Summarize the argument in a new "Variant metadata consistency" subsection of the Rationale, and cross-reference the appendix from the specification. Close the open issue on the use of variant environment markers. The investigation settles the question in favour of markers, so the Open Issues section is removed and the reasoning is recorded at the end of the "Variant environment markers" rationale instead.
Provide a high-level description of how ordering works and what it is meant to achieve, in addition to the precise algorithm provided right now. Add clarifications to the algorithm, to make it clear in what order the lists are actually arranged. Signed-off-by: Michał Górny <mgorny@quansight.com>
Signed-off-by: Michał Górny <mgorny@quansight.com>
Signed-off-by: Michał Górny <mgorny@quansight.com>
Signed-off-by: Michał Górny <mgorny@quansight.com>
Signed-off-by: Michał Górny <mgorny@quansight.com>
This mainly removes duplication in phrasing, so it should improve clarity while being less verbose.
Co-authored-by: Michał Górny <mgorny@quansight.com>
Co-authored-by: Michał Górny <mgorny@quansight.com>
- Use the ``nvidia`` namespace in the example. The rest of the PEP uses ``nvidia`` as the namespace with ``cuda_version_lower_bound`` and ``sm_arch`` as features within it; ``cuda`` was not a namespace anywhere else. - "this yields most preferred wheel" -> "the most preferred wheel". - Restore the second blank line before the "Ordering algorithm" heading, matching every other subsection that follows body text.
Replace the prose ordering example with Python code that sorts four variant wheels, and drop the "To express it with Python types" paragraph, which the code now covers.
State up front that variant wheels sort as Python sorts lists of tuples, pin the direction so the run-out case is unambiguous, and move the algorithmic spelling-out behind an explicit "Spelled out:" so readers can skip whichever version they don't need.
``gpu_v4`` reads as "version 4 of the GPU". Bind the microarchitecture level to the CPU part instead, giving ``gpu``, ``gpu_cpuv2``, ``gpu_cpuv4`` and ``cpuv4``.
Documentation build overview
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR collates several updates to PEP 825 (https://discuss.python.org/t/pep-825-wheel-variants-package-format-split-from-pep-817/106196).
Change History
26-Aug-2026
pep825-metadata-consistencyas an appendix, setting outwhy the
metadata consistency_ requirements are justified and whatthey cost. Summarized the metadata consistency argument in the
Rationale.
The investigation in the appendix settles the question in favour of
markers, so the Open Issues section has been removed and the
reasoning recorded in the Rationale instead.
tie-breaking along with other wheel properties. This reverts a
potential change in behavior for non-variant wheels.
clarified that the ordering of the lists used in the algorithm is
from the most preferable to the least preferable and that the
ordering by platform compatibility tags is not changed.