Skip to content

PEP 772: The PSF Board's latest resolution, along with the requested changes#4872

Merged
warsaw merged 7 commits intopython:mainfrom
warsaw:772-board-resolution
Mar 24, 2026
Merged

PEP 772: The PSF Board's latest resolution, along with the requested changes#4872
warsaw merged 7 commits intopython:mainfrom
warsaw:772-board-resolution

Conversation

@warsaw
Copy link
Member

@warsaw warsaw commented Mar 23, 2026

Board resolution as provided by Deb Nicholson via email. The board minutes for the meeting at which this was resolved is unpublished atm. This change also includes posting placeholders.


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

@warsaw warsaw self-assigned this Mar 23, 2026
@warsaw warsaw requested a review from pradyunsg as a code owner March 23, 2026 23:17
warsaw added 4 commits March 23, 2026 16:21
Happy to split this out into a separate PR, but check-peps.py should accept "Pending" as one entry in a
multi-line Post-History header, as is the case in PEP 772.
@warsaw
Copy link
Member Author

warsaw commented Mar 24, 2026

@AA-Turner @hugovk Note the change to check-peps.py to accept Pending as one line in a multi-line 'Post-History' header. I'm happy to split that out into a separate PR (or let y'all do it).

@AA-Turner
Copy link
Member

I think Post-History is/should be where the PEP has been posted for discussion, rather than an indication that the authors intend to post it again? As such I think it'd be simpler to forgo the pending header and just update next time the authors do post it?

A

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.

meant to approve barring the comment above; sorry!

Copy link
Contributor

@willingc willingc left a comment

Choose a reason for hiding this comment

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

Thanks @warsaw!

@warsaw
Copy link
Member Author

warsaw commented Mar 24, 2026

I think Post-History is/should be where the PEP has been posted for discussion, rather than an indication that the authors intend to post it again? As such I think it'd be simpler to forgo the pending header and just update next time the authors do post it?

I guess in that case it makes sense to only accept a single Post-History: Pending line rather than one of many, given that it's only pre-first-post that will have that line. Subsequent changes will just have to do the update-header-dance. Okay, let me back those changes out. Thanks!

@warsaw warsaw enabled auto-merge (squash) March 24, 2026 00:35
@warsaw warsaw merged commit 19216b0 into python:main Mar 24, 2026
4 of 5 checks passed
@warsaw warsaw deleted the 772-board-resolution branch March 24, 2026 00:46
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.

3 participants