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

Pants

I'd like to have broader `[python].interpreter_constraints` _and_ install a very specific version when I run `export` for a venv. How can I achieve this with the <https://www.pantsbuild.org/2.24/reference/subsystems/pyenv-python-provider|pyenv> provider?

You can pass the interpreter constraints on the cli.
Would something like `pants export --python-interpreter-constraints="[&lt;specific_version&gt;]"` work for your case?

(and keep the broad version in your `pants.toml`)

I guess my broader question is "how can I be flexible about what my code is run with when exported" and "specific about the version I use in testing"

I get in theory it "shouldn't matter", but I'd like to not have any variance between developers/CI

Would like to not have to specify a custom config or that setting in the command line each time.