-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
No such file or directory error when installing types with mypy #16767
Comments
It seemed that my previous pipeline jobs that were succeeding started failing so I look at the versions of the typing packages being installed and noticed these were updated since (working versions are below):
Locking the versions to the versions listed above fixed the error. I'm not sure what the issue is with the new typing packages, but it seems either mypy is pulling in incompatible versions or the there is a bug in latest version of one of the packages. |
@jakecyr thanks for your comment! it helped a lot. waiting until this is fixed now python/typeshed#11254 |
We ran into this as well and I drilled down into mypy since yesterday:
I'm just laying this out here because I'm now unsure which component is wrong exactly. The Edit: I guess my comment is more about the fact that mypy could handle this better, even if the linked typeshed issue gets fixed. |
@getim thanks for looking into it! While typeshed will need to be fixed, let's remove trailing slash in |
@hauntsaninja Sounds good, see here |
Additionally: - add unit test for new call. Includes some refractoring as new calls are ment to be new implementation of already exisiting calls. - add protobuf python compliled code with stubs in neptune.internal.proto with additional unit tests - pin types-protobuf in mypy pre-commit hook as a workaround to fresh protobuf-typing bug. More info: python/mypy#16767 - excluded proto files from flake8 check as they are output of protoc compiler and far from perfect syntax
Additionally: - add unit test for new call. Includes some refractoring as new calls are ment to be new implementation of already exisiting calls. - add protobuf python compliled code with stubs in neptune.internal.proto with additional unit tests - pin types-protobuf in mypy pre-commit hook as a workaround to fresh protobuf-typing bug. More info: python/mypy#16767 - excluded proto files from flake8 check as they are output of protoc compiler and far from perfect syntax
Bug Report
When running the command
poetry run mypy --config-file pyproject.toml
in GitLab CI, MyPy starts installing types as expected, but then throws an error:Expected Behavior
I would expect MyPy to install the required types and run the static analysis check.
Actual Behavior
Your Environment
This error occurs when running the mypy command in GitLab CI.
mypy.ini
(and other config files):The text was updated successfully, but these errors were encountered: