Zachary Ware

Ahh, I see now! I wonder if a better solution might be for @bedevere-bot to watch for the merge commits created by the button, and complain if they look abusive...

The goal here is to avoid the situation where for some months we offered the option of 3.13 in the `bug.yml` template (thanks to python/cpython#111083) but not the `crash.yml` template...

(Side note: why am I allowed to merge here? I would have thought this should be limited to RMs :))

See python/peps#4003 for the PEP-101 update.

I think we've quibbled enough on this; I'm merging it :). I'm re-running the new job one last time just to be sure, but setting automerge anyway. Since it's non-blocking...

> 5\. @zware's [open question](https://github.com/python/cpython/pull/135402#discussion_r2201979005) around 2.7 support I would support updating the compatibility comment to just "all currently-maintained versions" rather than listing any particular ones and modernizing accordingly.

Sidenote: I have a very hard time believing that there is any reasonable DOS in this code at all. Can someone please explain how it can be exploited?

I disagree. If it is non-exploitable, it's not a DOS. Fixing it only encourages further reports of invulnerable vulnerabilities and a waste of volunteer time. That said, there does appear...

Please don't keep merging main like that, it consumes CI resources unnecessarily. A merge is only really necessary to resolve conflicts or as a final check before merge, which is...

I'm not sure we need to get that specific here. Since we're here documenting that we expect the election service to break (some to all) ties, the service's tie-breaking scheme...