Skip to content

Conversation

@DEKHTIARJonathan
Copy link

@DEKHTIARJonathan DEKHTIARJonathan commented Dec 10, 2025

Basic requirements (all PEP Types)

  • Read and followed PEP 1 & PEP 12
  • File created from the latest PEP template
  • PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) and PEP header
  • Title clearly, accurately and concisely describes the content in 79 characters or less
  • Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval
  • Author, Status (Draft), Type and Created headers filled out correctly
  • PEP-Delegate, Topic, Requires and Replaces headers completed if appropriate
  • Required sections included
    • Abstract (first section)
    • Copyright (last section; exact wording from template required)
  • Code is well-formatted (PEP 7/PEP 8) and is in code blocks, with the right lexer names if non-Python
  • PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML
  • Authors/sponsor added to .github/CODEOWNERS for the PEP

Standards Track requirements

  • PEP topic discussed in a suitable venue with general agreement that a PEP is appropriate
  • Suggested sections included (unless not applicable)
    • Motivation
    • Rationale
    • Specification
    • Backwards Compatibility
    • Security Implications
    • How to Teach This
    • Reference Implementation
    • Rejected Ideas
    • Open Issues
  • Python-Version set to valid (pre-beta) future Python version, if relevant
  • Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
  • Right before or after initial merging, PEP discussion thread created and linked to in Discussions-To and Post-History

CC: @mgorny @konstin @rgommers @atalman @charliermarsh @msarahan @seemethere @warsaw @dstufft @aterrel


📚 Documentation preview 📚: https://pep-previews--4740.org.readthedocs.build/pep-0817/

@DEKHTIARJonathan DEKHTIARJonathan requested a review from a team as a code owner December 10, 2025 21:54
@python-cla-bot
Copy link

python-cla-bot bot commented Dec 10, 2025

All commit authors signed the Contributor License Agreement.

CLA signed

@hugovk
Copy link
Member

hugovk commented Dec 10, 2025

Let's renumber this to 9999 for now, we also have #4739 clashing.

@warsaw or @dstufft Please can you confirm co-authorship?

@hugovk hugovk changed the title PEP 817: Wheel Variants: Beyond Platform Tags PEP 9999: Wheel Variants: Beyond Platform Tags Dec 10, 2025
@DEKHTIARJonathan
Copy link
Author

Oh thanks @hugovk I totally didn't see that one being published within 20min :D

Let me know which number you want me to pick and I'll do the update ;)

@warsaw
Copy link
Member

warsaw commented Dec 10, 2025

@warsaw or @dstufft Please can you confirm co-authorship?

Confirmed.

@hugovk hugovk changed the title PEP 9999: Wheel Variants: Beyond Platform Tags PEP 817: Wheel Variants: Beyond Platform Tags Dec 10, 2025
@hugovk
Copy link
Member

hugovk commented Dec 10, 2025

Thanks!

@DEKHTIARJonathan You may continue with 817.

@AA-Turner AA-Turner added the new-pep A new draft PEP submitted for initial review label Dec 11, 2025
Copy link
Member

@AA-Turner AA-Turner left a comment

Choose a reason for hiding this comment

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

very brief review, I haven't yet read beyond the end of Motivation.

A

@jezdez
Copy link

jezdez commented Dec 11, 2025

Just a brief bystander comment: I'm so stoked to see this PEP draft published!

@DEKHTIARJonathan
Copy link
Author

Just a brief bystander comment: I'm so stoked to see this PEP draft published!

Thanks Jannis! Took some significant amount of work but we eventually got there

Signed-off-by: Michał Górny <[email protected]>
Reflow the text to restore correct text width after all the inline
changes and applied suggestions.

Signed-off-by: Michał Górny <[email protected]>
Signed-off-by: Michał Górny <[email protected]>
Remove accidental double spaces that vim's `gq` introduced while I was
reflowing the text.  Thanks to @konstin for noticing.

Signed-off-by: Michał Górny <[email protected]>
enabling the optional provider or selecting the variant explicitly.


Package ABI matching

Choose a reason for hiding this comment

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

Super excited about this one by the way :D

mgorny and others added 27 commits December 30, 2025 15:28
This reverts commit 261704f.

Signed-off-by: Michał Górny <[email protected]>
Signed-off-by: Michał Górny <[email protected]>
Signed-off-by: Michał Górny <[email protected]>
Signed-off-by: Michał Górny <[email protected]>
Environment marker usage and optionality is described in "Providers"
section. Let's limit "Provider information" only to technical field
details themselves.

Signed-off-by: Michał Górny <[email protected]>
@AA-Turner
Copy link
Member

I took a brief break over Christmas, aiming to look over the updates tomorrow (Saturday 3rd).

A

@mgorny
Copy link
Contributor

mgorny commented Jan 6, 2026

Thanks. At this point, it might be easier to look through the whole thing. I'm really looking forward to feedback whether the new version, when read top-to-bottom, makes concepts clearer without having to go back and forth, as it was necessary with the previous version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-pep A new draft PEP submitted for initial review

Projects

None yet

Development

Successfully merging this pull request may close these issues.