-
Notifications
You must be signed in to change notification settings - Fork 22
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
Avoid conflicts when function is implemented in same-named submodule #9
Avoid conflicts when function is implemented in same-named submodule #9
Conversation
assert isinstance(fake_pkg.some_func, types.FunctionType) | ||
assert isinstance(fake_pkg.some_func, types.FunctionType) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we test that from fake_pkg.some_func import some_func
also works?
In codebases where this happens, some people do from fake_pkg import some_func
and some do from fake_pkg.some_func import some_func
and both work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, I added a test for that.
any updates on a timeline for this change? |
Merged, let's see how it goes. |
awesome :) Do you anticipate a new rc release with this in the immediate future? |
@TortoiseHam Please open an issue if you run into any issues: |
@adrinjalali It would be great if you could test out: |
Supersedes #8