I'm trying to understand the `mypy` tool behavior,...
# general
f
I'm trying to understand the
mypy
tool behavior, and I'm unclear from the current docs and I'm not sure if the GitHub issues I've found are outdated: does pants' mypy setup use whichever mypy configuration is found closest to the source it is run against? Or is it a single mypy config for the entire repo? I've seen some older GH issues, but they seem to mainly discuss the need for partitioning requirements, rather than config inheritance itself.
While I would love to have partitioned tool requirements, my main question at the moment is just how mypy configs are handled in a monorepo.
k
f
I saw that config, but then after reading open GH issues like this one, and checking the source code it seems that mypy does not offer any kind of multi-config setup even with the
[mypy].config_discovery
setting enabled. The relevant bits of code: 1. the mypy fieldset's config_request method 2. the find_config_file rule
I've created an issue here. I think this is partially a documentation problem, and partially a deviation from mypy's definition of "config discovery".