-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Module "jaraco" has no attribute "env" (from jaraco import env) #15970
Comments
Removing the
|
Note that |
Here's something interesting. If I install
It only occurs if |
I am able to replicate the issue more simply, without the official versions of jaraco.functools or jaraco.env with empty modules thus:
|
Suppress the spurious error from mypy as reported in python/mypy#15970. Closes #22.
Suppress the spurious error from mypy as reported in python/mypy#15970. Closes #79.
My guess: both |
likely duplicate of #10360 |
Bug Report
In jaraco/pip-run#79, I noticed that the mypy tests started failing and traced the emergent failure to enhancements in the typing of a sibling submodule.
To Reproduce
Run instead with
jaraco.functools<3.9
and mypy succeeds:jaraco.functools 3.9 moved functools to its own submodule and declared that module as typed (jaraco/jaraco.functools#22).
Expected Behavior
Changes to a sibling submodule shouldn't affect the reliable checking when importing a module. mypy should detect
from module import submodule
as valid.Your Environment
mypy.ini
(and other config files): none in repro, but some in project.The text was updated successfully, but these errors were encountered: