Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Failing to lock `mypy` when adding a py3.7+ dep? `The current project's Python requirement (&gt;=3.6)`  I thought Pants was 3.7+?

All the lockfiles seem to say:
`valid_for_interpreter_constraints..."CPython&lt;4,&gt;=3.6"`

I would've expected the same value as `pants.toml`'s `interpreter_constraints`

Oh some of them are different, but `mypy`'s is 3.6

It seems that `mypy` doesn't inherit `python` 's `interpreter_constraints`.
<@UB2J9BQA0> should it?

It's complicated. That option is what to install and run MyPy itself with, which can be different than the version of Python MyPy targets the code for

We dynamically determine what version of Python MYpy should target via `[python].interpreter_constraints` option + field.

But for what to run the tool, we use `[mypy].interpreter_constarints`. If you have the default, we also check if your code is exclusively Py38+ and update the default constraints to match that if so, because MyPy run with &lt;38 cannot target code &gt;=38