Is there a way in `pants test` to filter by interp...
# general
v
Is there a way in
pants test
to filter by interpreter_constraint? Background: Adding version support and testing with a BUILD file like:
Copy code
__defaults__( {
  python_test: {
    "interpreter_constraints": parametrize(py310=["==3.10.*"], py311=["==3.11.*"]),
   } )
And then I could run an individual test file with something like
Copy code
pants test runtime/my_test.py:tests@interpreter_constraints=py311

# and even multiple tests in a folder where tests are defined
pants test runtime/:tests@interpreter_constraints=py311
but going one level higher - to a folder that contains multiple folders of tests, that
interpreter_constraint
selection does not seem to work. The short term goal of this is - to be able to run some tests without having all relevant versions of python installed.
I think I found a workaround where parametrize can set the interpreter_constraints and a tag together: https://www.pantsbuild.org/blog/2024/01/24/pants-2-19#improved-parametrize-for-tied-options