Skip to content

Conversation

@zware
Copy link
Member

@zwarezware commented Sep 27, 2024

  • Change is either:
    • To a Draft PEP
    • To an Accepted or Final PEP, with Steering Council approval
    • To fix an editorial issue (markup, typo, link, header, etc)
  • PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

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

Copy link
Member

@ned-deilyned-deily left a comment

Choose a reason for hiding this comment

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

LGTM. I suggest also opening an issue in python/release-tools to automate this step in release.py.

@zware
Copy link
MemberAuthor

I failed to cross-link the other direction; see python/release-tools#170 where @hugovk requested this one :)

Copy link
Member

@hugovkhugovk left a comment

Choose a reason for hiding this comment

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

Thank you!

@hugovkhugovk merged commit cb97c7c into python:mainSep 27, 2024
@zwarezware deleted the pep101_add_issue_templates branch September 27, 2024 18:53
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

@zware@hugovk@ned-deily