Skip to content

Conversation

StanFromIreland
Copy link
Member

@StanFromIreland StanFromIreland commented Sep 8, 2025

  • 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--4580.org.readthedocs.build/

@pablogsal pablogsal merged commit 33a7a06 into python:main Sep 8, 2025
6 checks passed
@StanFromIreland StanFromIreland deleted the 679/discussion-link branch September 8, 2025 19:41
Author: Pablo Galindo Salgado <pablogsal@python.org>,
Stan Ulbrych <stanulbrych@gmail.com>,
Discussions-To: Pending
Discussions-To: https://discuss.python.org/t/pep-679-new-assert-statement-syntax-with-parentheses/103634
Copy link
Member

Choose a reason for hiding this comment

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

Please also add this to Post-History.

Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

It's a requirement per PEP 1 & 12. Post-History tracks major discussions, potentially including prior to drafting as a PEP. Discussions-To is the forum for current discussions. The former is far more important from a history and archives perspective.

A

Copy link
Member Author

Choose a reason for hiding this comment

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

I understand that, and I don't mind doing it, I can do it immediately, or wait a while and bundle it with other changes, whichever you prefer.

But out of curiosity, why was this not done here: #4578?

Copy link
Member

Choose a reason for hiding this comment

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

That was a mistake on my side. I'll correct it in the next update.

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