-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PEP 13: Add STAR voting and misc tidbits #3958
base: main
Are you sure you want to change the base?
Conversation
This is the 21st century. Co-authored-by: Éric <[email protected]>
@@ -343,6 +353,7 @@ History of amendments | |||
--------------------- | |||
|
|||
2019-04-17: Added the vote length for core devs and changes to this document. | |||
2024-XX-XX: Adopted Multi-winner Bloc STAR voting for council elections. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember to fill in the actual date the PR was approved by a Discord poll (or some other significant date, maybe just the date the PR is merged).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can link to https://discuss.python.org/t/changing-pep-13-to-adopt-bloc-star-voting/64971 here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This suggestion uses a footnote -- I couldn't think of a nice way to incorporate the link other than linking the whole line or having a '(link)' trailer, which we try to avoid.
2024-XX-XX: Adopted Multi-winner Bloc STAR voting for council elections. | |
2024-10-09: Adopted Multi-winner Bloc STAR voting for council elections. [1]_ | |
.. [1] https://discuss.python.org/t/64971 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the PEP metadata, the dates in post-history are links to changesets, so the date could be made a link here too, unless you think it’s not intuitive.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's more appropriate for this to link to the vote that approved the change. The changeset/PR can easily be retrieved using GitHub or git blame
; there's no easy wat to find the voting thread without explicitly linking it here.
Question for the SC (primarily): If I were to commit this today, it would appear to affect the upcoming election for SC2025. That's not a good idea, because we'd have to scramble to figure out exactly how to run the election. So my plan has always been to make this go into effect for the election after the upcoming one, voting for SC2026. I can think of a few ways to implement that plan:
What would the current SC prefer that I do? |
I made a mistake here -- since PEP 13 defines the SC's powers, it's inappropriate for the SC to be involved here. I've decided to just postpone committing this PR until the upcoming election is done. See the discussion in Discourse. |
PEP 123: Summary of changes
)📚 Documentation preview 📚: https://pep-previews--3958.org.readthedocs.build/pep-0013/