Repository navigation
gh-84644: Don't single-dispatch on return types - #140255
Closed
johnslavik wants to merge 3 commits into
Closed
johnslavik wants to merge 3 commits into
johnslavik wants to merge 3 commits into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
johnslavik
commented
Oct 17, 2025
Comment thread
Lib/functools.py
Copy link
Copy Markdown
Member
Author
|
If we accept this, it could be a new ground to take over #130829 -- Peter has said he isn't planning on finishing that anytime soon. |
Sorry, something went wrong.
Comment thread
Lib/functools.py
Copy link
Copy Markdown
Member
Author
|
Closing this to look for a general fix of how annotations are inspected -- see #140255 (comment) |
Sorry, something went wrong.
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
Reviewers
2 participants
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.
Prior art is #19871, but it widened its scope to also fix issue #130827 that hadn't yet been reported back then.
This PR does not fix issue #130827.
I'm specifically only trying to close the issue #84644.