Skip to content

Conversation

@hugovk
Copy link
Member

@hugovkhugovk commented Jun 1, 2024

  • Final implementation has been merged (including tests and docs)
  • PEP matches the final implementation
  • Any substantial changes since the accepted version approved by the SC/PEP delegate
  • Pull request title in appropriate format (PEP 123: Mark Final)
  • Status changed to Final (and Python-Version is correct)
  • Canonical docs/spec linked with a canonical-doc directive
    (or canonical-pypa-spec for packaging PEPs,
    or canonical-typing-spec for typing PEPs)

Helps #2872, which says:

PEP-581Using GitHub Issues for CPython: Since the PEP's content is tightly focused on the rationale for choosing GitHub rather than the current, active process for using it and is thus now of historical rather than procedural value, it should be marked Final (rather than Active) like other transition-oriented Process PEPs have.

Also remove some redundant fields.


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

@hugovkhugovk requested a review from Mariatta as a code ownerJune 1, 2024 20:21
@hugovkhugovk mentioned this pull request Jun 1, 2024
12 tasks
Copy link
Member

@MariattaMariatta left a comment

Choose a reason for hiding this comment

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

Thanks

@hauntsaninjahauntsaninja merged commit 097f2d8 into python:mainJun 2, 2024
@hugovkhugovk deleted the pep581-mark-as-final branch June 2, 2024 07:24
Sign up for freeto 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

@hugovk@Mariatta@hauntsaninja