Skip to content

Conversation

@hugovk
Copy link
Member

@hugovk hugovk commented Apr 9, 2025

There's often confusion about whether the discussion thread should be created before or after the draft PEP has been merged.

It's often better to merge the PEP first, and the the thread can use the https://peps.python.org/ URL instead of disseminating a temporary RTD URL that will soon be outdated and later deleted.

The linter is confusing too: "Discussions-To must be a valid thread URL or mailing list" makes some think the thread must be created first to pass, it's not obvious they can omit the field to satisfy the linter.

Finally, PEP 12 says "it is okay to just list the venue name initially" but the linter requires a thread or ML URL.

Instead, I think it may improve things if authors can write "Discussions-To: TBA" "Discussions-To: Pending" without the linter complaining. We can then merge the draft PR, they can open the thread, and then replace the TBA Pending.


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

@Rosuav
Copy link
Contributor

Rosuav commented Apr 9, 2025

👍 Definitely in favour.

@warsaw
Copy link
Member

warsaw commented Apr 9, 2025

Huge +1, as there's always the "publish PEP, start the DPO thread, update the PEP dance"

That said, I'd bikeshed against using an initialism, and just go with "Pending"

Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
@hugovk hugovk changed the title PEP 12: Allow "TBA" as Discussions-To PEP 12: Allow "Pending" as Discussions-To Apr 10, 2025
@brettcannon brettcannon merged commit ccd8257 into python:main Apr 10, 2025
22 checks passed
@brettcannon
Copy link
Member

I went ahead and merged as Barry and I were +1 and everyone overall seemed positive on the idea.

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