Repository navigation
TYP: fix complex_sort for builtin sequences - #31917
Merged
charris merged 1 commit intoJul 8, 2026
Merged
Conversation
jorenham
added
09 - Backport-Candidate
Member
|
Thanks Joren. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
complex_sortaccepts builtin scalar sequences at runtime :But the stubs rejected this, so this adds an additional overload to handle this case.
Fully written by me (a human); bug found by Claude Fable 5 (here's the full (second) audit for those interested).
(even more stub fixes on the way)