#17749 Ability to run different mypy partitions-by-config in different resolves Issue created by mpcusack-color An extension of #17739. The full problem is laid out here. We would like to use mypy_django_plugin for a subset of our repo. The first step of this is the ability to partition the

check

goal by different

mypy

configuration so we can only optionally enable the plugin. Even after this is accomplished the problem remains that in order to function the plugin requires that the entire django project be included in the

mypy

resolve. We are willing to take this

check

performance hit for the django code, but not for the rest of our codebase (the django project is large and pulls in ~150 3rdparty deps). I would like to be able to have multiple mypy resolves with different

extra_requirements

and specify which to use for the different mypy configs. pantsbuild/pants