sorted() does not enforce comparable items in an iterable of tuples is fixed #13297 #13303
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.
I’ve added an overload for the sorted() function that explicitly handles tuples with elements that support SupportsRichComparison. This ensures that the tuples only contain comparable elements, and the type checker will catch any issues before runtime.
Explain :
Added a Specialized Overload for Tuples:
The third overload explicitly specifies that when sorting tuples, all elements in the tuple must satisfy SupportsRichComparison.
This ensures that sorted only works for tuples where every element is fully comparable.If a key function is provided, the burden of ensuring comparability is transferred to the result of the key function.