-
Notifications
You must be signed in to change notification settings - Fork 238
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
Control flow incorrect if imported functions have the same name #197
Comments
wchresta
added a commit
to wchresta/pyt
that referenced
this issue
Mar 23, 2019
This checks imports of functions with name collisions are resolved correctly.
wchresta
added a commit
to wchresta/pyt
that referenced
this issue
Mar 23, 2019
This checks imports of functions with name collisions are resolved correctly.
Just read your code that fixes this, it is awesome :) |
@KevinHock sadly I was so far unable to fix this for the moment. I'll try to look into this after #177 and #180. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When there are two modules that expose a function with the same name, and those get imported directly (using aliases), the control flow is resolved incorrectly.
Example:
module_a.py
module_b.py
test.py
This will lead to a control flow that calls the function
module_a.foo
twice instead of once for each version.The text was updated successfully, but these errors were encountered: