Hey! I ran across a general question on pants that I'm not sure about. If you put

[python].intepreter_constraints

does it require a python version for pants-commands themselves, i.e. for the pantsd or cli? We ran into it when having lockfiles being generated out-of-order on a box with a python version < 3.7 due to what we think is just python version handling dict ordering differently. However we have provided python version constraints >= 3.7, but they seem to be only asserted for

pants fmt

, not

pants check, test or generate-lockfiles

. Am I missing some global constraint option?

See https://github.com/pantsbuild/scie-pants/

Yeah but we have a mix of environments like

asdf

,

nix

etc. So I was mostly curious if pants enforces the constraint or if we should enforce it on top as well

My point is that the Python used by Pants itself is kept completely separate from the issue of how Python is chosen for the user's code (including any of the related config options). The launcher binary will never look at

[python].intepreter_constraints

.

Okay thanks, that was what I was thinking but wasn't entirely sure