-
-
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
Docs for --install-types
do not explain no mypy cache directory
error
#10863
Comments
Updated our
that got our CI green, would be a good default imo (e.g. behind the |
MyPy expects the cache directory to be there. We now remove it after each super-linter run to avoid leftovers, so we need to create it before runniny MyPy. See python/mypy#10768 and python/mypy#10863
MyPy expects the cache directory to be there. We now remove it after each super-linter run to avoid leftovers, so we need to create it before running MyPy. See python/mypy#10768 and python/mypy#10863
MyPy expects the cache directory to be there. We now remove it after each super-linter run to avoid leftovers, so we need to create it before running MyPy. See python/mypy#10768 and python/mypy#10863
Is this fixed? I'm encountering the same error. |
I am still encountering the same error. |
Documentation
Docs for
--install-types
and--non-interactive
do not mention.mypy-cache
yet these options often fail (esp. in GitHub Actions, tox, pre-commit) witherror: --install-types failed (no mypy cache directory)
even aftermkdir .mypy_cache
has been run. The user may then experience a tremendous feeling of helplessness.Probably caused by #10768 but the docs should help the user understand the misleading error message.
The text was updated successfully, but these errors were encountered: