Skip to content

Conversation

@Wulian233
Copy link
Contributor

@Wulian233 Wulian233 commented Mar 15, 2025

  • SC/PEP Delegate has formally accepted/rejected the PEP and posted to the Discussions-To thread
  • Pull request title in appropriate format (PEP 123: Mark as Accepted)
  • Status changed to Accepted/Rejected
  • Resolution link points directly to SC/PEP Delegate official acceptance/rejected post
  • Acceptance/rejection notice added, if the SC/PEP delegate had major conditions or comments
  • Discussions-To, Post-History and Python-Version up to date

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

@AA-Turner
Copy link
Member

AA-Turner commented Mar 15, 2025

@Wulian233, for the future, we generally we let the PEP author create the PR to mark as accepted, as they might have other tidying up to do.

A

Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
@CAM-Gerlach
Copy link
Member

Indeed, and there's also a checklist for doing so (added automatically by selecting the correct PR template):

  • SC/PEP Delegate has formally accepted/rejected the PEP and posted to the Discussions-To thread
  • Pull request title in appropriate format (PEP 123: Mark as Accepted)
  • Status changed to Accepted/Rejected
  • Resolution link points directly to SC/PEP Delegate official acceptance/rejected post
  • Acceptance/rejection notice added, if the SC/PEP delegate had major conditions or comments
  • Discussions-To, Post-History and Python-Version up to date

@Wulian233
Copy link
Contributor Author

Thank you for the reminder. I have revised the PR description

@brettcannon brettcannon merged commit 4a65966 into python:main Mar 17, 2025
5 checks passed
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.

5 participants