Issues with popular third-party packages (meta)

[JukkaL]

This issue is used to centrally track issues related to using mypy together with popular third-party packages (either using inline types or stubs). These issues can impact a large number of users, and thus we generally prioritize fixing them. However, sometimes we can lose track of some problems, and this issue is intended to help with that.

Issues could be anything interfering with the use of mypy with a third-party package, including but not limited to these:

• Mypy crashes
• False positives
• Slow type checking

If you encounter something like the above, create a separate issue first and leave a comment here with a link to the issue, preferably in this format so the status of issue is immediately visible:

• Support with statements #123

Also feel free to post links to existing issues created by others, so that they will get more visibility.

[hauntsaninja]

• mypy is slow when type checking torch #17919

[brianschubert]

• Mypy stuck with polynomial using NumPy #14978

[hauntsaninja]

Crash involving numpy

• mypy --follow-imports error or skip crashes with numpy 2.0.0 #17396

[hauntsaninja]

mypy has an incremental bug related to namespace packages. It comes up in a few places, but a lot of times with the popular ruamel.yaml package:

• Incremental parsing issue with namespace packages #12664

[hauntsaninja]

Nondeterministic type checking (with cache off) involving pydantic:

• Type error randomly raised when using a decorator and a type: ignore comment #18125