Skip to content

Conversation

@zware
Copy link
Member

@zware zware commented Oct 24, 2025

This change requires a vote among the core team before it can be merged. Once the poll is opened, the history of amendments note will be amended to include the correct date of the poll closure and a link to the poll.


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

Copy link
Member

@tim-one tim-one left a comment

Choose a reason for hiding this comment

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

LGTM! Thank you 😄

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 @zware. Love the simple and direct wording.

@warsaw warsaw self-requested a review October 24, 2025 18:29
Copy link
Member

@warsaw warsaw left a comment

Choose a reason for hiding this comment

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

I also like the simple wording. One thing that occurs to me is that the wording here means that all ties (even mid-resolution ties) can be resolved by the software. I think that's fine.

@tim-one
Copy link
Member

tim-one commented Oct 24, 2025

@warsaw

One thing that occurs to me is that the wording here means that all ties (even mid-resolution ties) can be resolved by the software. I think that's fine.

I believe it's essential. The BetterVoting software has no possibility to pause "in the middle" of scoring to wait for human input on how to resolve a tie.

For a 5-winner SC election, if the winner of the 5th round was picked via breaking a tie, then it would be reasonable to let the tied candidates decide among themselves who gets the seat, and ignore the software's pick. But I wouldn't want to complicate the PEP to cater to that.

There's no real need anyway. If the ballots themselves don't contain enough info to break a tie, "the community" has expressed no preference. "Random" is as good as it gets then.

@tim-one
Copy link
Member

tim-one commented Oct 26, 2025

This hasn't seen new activity in a few days, and nothing but approvals. Time for the poll? Note that Guido withdrew his offer to run the poll,, so someone else will need to step up to do that.

@tim-one
Copy link
Member

tim-one commented Oct 28, 2025

@zware, are you still working on this, or is it ready for a poll?

@AA-Turner
Copy link
Member

Is there a succinct phrasing to capture that the automatic resolution of ties by the voting system ought be 'fair', explicitly random, or etc? A valid solution to breaking ties would be simply to pick the candidate who's surname is first alphabetically, but obviously we'd not want to use anything like this.

A

@zware
Copy link
Member Author

zware commented Oct 28, 2025

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 just becomes part of the implicit selection criteria for the service. I don't think we'd choose to use a service with insane tie-breaking (though as Tim has said, a tie means there's actually no preference, so choosing the first alphabetically by middle initial isn't as insane as it looks at first glance...as long as it's choosing one of the tied candidates :) ).

@zware, are you still working on this, or is it ready for a poll?

I think we're ready for a poll, which I'd prefer not to drive but can if I must. Once it's open I'll update the amendment note with the correct date and link.

@tim-one
Copy link
Member

tim-one commented Oct 28, 2025

FYI, I posted a poll just now:

https://discuss.python.org/t/vote-changing-pep-13-to-clarify-tiebreaking-for-sc-elections/104607

Adopted Multi-winner Bloc STAR voting for council elections.
* `2024-12-10 <https://discuss.python.org/t/72293/4>`__:
Added a one-week deadline for seconding a vote of no confidence.
* `2025-11-11 <https://discuss.python.org/t/104607>`__:
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
* `2025-11-11 <https://discuss.python.org/t/104607>`__:
* `2025-11-12 <https://discuss.python.org/t/104607>`__:

To match the poll end date:

EDIT: the poll is configured to close at 2025-11-12T06:00:00.000Z. Why? “About two weeks” from its posting date. If people want to dispute that, please supply the precise string you’d like to see instead. Note that results won’t be visible (not even to me) until the poll closes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants