The Pylance team at Microsoft seems to have produced pretty good type stubs for matplotlib: https://github.com/microsoft/python-type-stubs/tree/main/matplotlib

With pandas, we created a pandas-stubs project https://github.com/pandas-dev/pandas-stubs that evolved as follows:

We started with the stubs that Microsoft was maintaining as part of https://github.com/microsoft/python-type-stubs/
In that project, we merged in tests from https://github.com/VirtusLab/pandas-stubs to provide a testing framework for the stubs.
We met with the leader of the Microsoft project and VirtusLabs and agreed that the pandas team would start supplying the stubs, that the pandas stubs would be removed from the Microsoft project, and that VirtusLabs would deprecate their stubs.
The pylance team now bundles the "official" pandas-stubs with pylance.

I would suggest a similar path for matplotlib. Create a matplotlib-stubs project, and work with Microsoft to use their stubs as a starting point. You might also consider looking at what we are doing in pandas-stubs to create a testing methodology for correctness of the stubs.

Uh oh!

Support type checking with mypy #20504

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions