overload tracing decorator to preserve type info #9994
Merged
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.
This resolves the issue I was seeing in #9989 and passes all unit tests locally, but deserves some extra scrutiny given how ubiquitous it is in the codebase.
Some notes:
The double under in
__func
appears to be necessary to help inform mypy that that parameter is intended as positional only, to allow the overloads to be resolvable (ref: https://www.python.org/dev/peps/pep-0484/#positional-only-arguments)Similarly absent being able to specify real kwarg-only params,
name_of_span
of span had to be moved to kwargs for the overloads to be resolvableThere don't appear to be any tests for the async decorator