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
INTERNAL ERROR: AssertionError: ClassDef is lacking info #15804
Comments
Appreciate all the work from the mypy team, if there's anything else I can provide let me know! Sorry if this is a dup. |
I think this has something to do with Pydantic 2.0's |
Chances are this is a bug in pydantic's mypy plugin, which is maintained by the Pydantic project, not by mypy itself. |
Hi, maybe this is an instance of pydantic/pydantic#6985? While the manifested error is different it's the exact same code path in the pydantic plugin...? |
I think the MR linked in that issue (pydantic/pydantic#7002) does fix this, from some local testing I did. |
Closing as this is a bug in pydantic, not mypy. |
Crash Report
I am seeing a Mypy INTERNAL ERROR on both
1.4.1
and1.6.0+dev.54bc37ccade0476a1738b33cd34b6eb35d7124e1
.I don't see it on first run of
mypy
immedaitely after clearing.mypy_cache
, but I see it on all runs after that first one.Relatively minimal info to reproduce, at least for me:
This python file,
config.py
:This mypy configs file:
With these dependencies:
This command:
Traceback
To Reproduce
Above setup, with
Your Environment
1.6.0+dev.54bc37ccade0476a1738b33cd34b6eb35d7124e1
AND1.4.1
mypy --config pyproject.toml --show-traceback config.py
The text was updated successfully, but these errors were encountered: