Skip to content

PEP 825: add explicit "implementation requirements" - #64

Merged
mgorny merged 2 commits into
pep-wheel-variants-acceptancefrom
pep-825-consistency-reqs
Jul 24, 2026
Merged

PEP 825: add explicit "implementation requirements"#64
mgorny merged 2 commits into
pep-wheel-variants-acceptancefrom
pep-825-consistency-reqs

Conversation

@mgorny

@mgorny mgorny commented Jul 21, 2026

Copy link
Copy Markdown

No description provided.

Signed-off-by: Michał Górny <mgorny@quansight.com>
Comment thread peps/pep-0825.rst Outdated
@read-the-docs-community

read-the-docs-community Bot commented Jul 21, 2026

Copy link
Copy Markdown

Documentation build overview

📚 wheelnext-peps | 🛠️ Build #33691885 | 📁 Comparing 567a166 against latest (0cde95d)

  🔍 Preview build  

751 files changed · + 2 added · ± 749 modified

+ Added

± Modified

Co-authored-by: konsti-openai <konsti@openai.com>

@rgommers rgommers left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @mgorny. This seems entirely reasonable, and useful to add what should happen for invalid metadata.

If this is addressing a specific (couple of) comment(s) on DPO, it'd be useful to link to it in the PR description.

@mgorny

mgorny commented Jul 24, 2026

Copy link
Copy Markdown
Author

No specific comment; more like reading the atmosphere (and actually, it's something I felt we needed addressing for a while now, just didn't have a good idea how).

@mgorny
mgorny merged commit ea63380 into pep-wheel-variants-acceptance Jul 24, 2026
7 checks passed
@mgorny
mgorny deleted the pep-825-consistency-reqs branch July 24, 2026 02:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants