Development Tasks

This page lists task ideas for contributors. If you would like to try working on a task:

1. Add it to the issue tracker (if it's not already there). If there is an existing issue, check that nobody is assigned to the task or has added a comment about working on the task. If you are going to work on a big change, you should probably get an okay from a core developer before proceeding, as your change may not align with the objectives of mypy and may get rejected, or everybody may be busy and can't review your change until much later (or never).
2. You may want to add a comment to the issue tracker indicating that you are working on the issue. If you are a collaborator, you can also assign yourself to the task using the issue tracker.
3. Start coding!

You can also just start coding, but then there is a small risk that there will be duplicate work.

Also have a look at the issue tracker; it contains additional tasks.

Small tasks

Fix bugs

• Fix some bugs reported in the issue tracker. Issues with the 'easy' label are particularly good starting points.

Add stubs for Python modules

• Mypy needs interface stubs for library modules to type check code that uses those modules. Developing stubs is a relatively easy way to get familiar with the type system. See the stubs/3.2 directory for examples.

Determine test coverage for the mypy test suite

• Choose a Python test coverage tool and evaluate the test coverage of the mypy test suite. We can then analyze the results and figure out which parts of the codebase need more tests.