-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
typing.get_type_hints not working with forward-declaration and decorated functions #82019
Comments
When decorating a function and using a forward declaration as type hint, the typing.get_type_hints function does not work anymore, since it cannot find the forward declared name in the namespace. After debugging I think, the typing.get_type_hints function is actually using the namespace of the decorator instead of the decorated function. When using a normal class type (no forward declaration) everything works fine and also when not using any decorator it works like expected. As a workaround, one could pass the local namespace to typing.get_type_hints. However in normal usecases this function is used for runtime typechecking in a deep call hierarchy. So one would normally not have access to the right local namespace, only to the function object itself. However there is another easy workaround. At least when using the functool.wraps method to create a function decorator. The decorated functions has a "__wrapped__" attribute, which references the original function. When using "typing.get_type_hints(function.__wrapped__)" instead of "typing.get_type_hints(function)", it works like expected. So maybe this could be built in into the get_type_hints method. |
Using Netzeband, have you considered submitting a PR with the necessary changes (and tests and docs)? |
Yeah, I like this idea, this will likely cover most use cases (since most people actually do use @wraps). |
Maybe we should tag this issue "newcomer friendly"? It seems a pretty open |
Thanks for your feedback. I can create a pull-request. However, I did it never before for the Python-Lib, so I first have to setup the correct environment for that and ensure, that I can run all test-cases. Since I'm on vacation soon, it could take several weeks. If someone wants to solve the issue earlier, please don't hesitate. I will write it in this issue ticket, as soon as I finished the PR. |
Hey Netzeband, are you still working on this, or would it be ok for me to have a go? If all you needed was help with a PR let me know, i have some experience? |
@benedwards14 Feel free to open a PR. @netbnd said anyone can take on the issue since he may take long to revert with a PR. |
Actually there is a patch. So please @netbnd please open a PR https://github.com/python/cpython |
Hello, I'm very sorry, I was not able to find the time to finish the patch in the quality I wanted to have. So @benedwards14 please feel free to provide a pull request. Best regards, |
Thanks Netzeband, Will get on this. Ben |
Thanks a lot! |
The PR was linked by mistake (it is for a different issue), so I unlinked it. |
Have opened a PR, let me know if there is anything that needs fixing |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: