As mentioned in this comment #4315 (comment), there's going to be problem when running mypy in pre-commit.

The problem with running mypy in pre-commit is that pre-commit runs every hook in its own virtual environment and as mypy needs the information from project dependencies, they need to be installed there as well. pre-commit does provide an option: - additional_dependencies: ['numpy', ...] but that would mean we need to maintain the dependencies in requirements.txt and in pre-commit-config.yaml.

- repo: https://github.com/pre-commit/mirrors-mypy
    rev: v0.812
    hooks:
      - id: mypy
        additional_dependencies: [numpy, beautifulsoup4, requests, ...]

Ref:

• https://pre-commit.com/#config-additional_dependencies
• https://github.com/pre-commit/mirrors-mypy#using-mypy-with-pre-commit (3rd point)

mypy or any other type checkers should be run in an environment which contains the project dependencies for it to correctly report errors. If we are using any function/class/variable from other modules then mypy will know whether we are passing the correct type of arguments or assigning the correct type to the variable, etc.

This will be easier to understand when we start running mypy in a strict fashion as I am for algorithms-keeper. I faced the same issue when using mypy in pre-commit for the bot. At the end, it was either of the options:

1. Run mypy in pre-commit with specifying the additional_dependencies
2. Run mypy as a local hook in pre-commit
3. Run mypy in CI

Makes sense.