Hello, I have a problem with the plugins and how the dependencies to those are resolved. I have a plugin requiring a package that is available only for python3.9. Pants seems to run the pip command with python3.7, so pip tells me there is no package matching the requirements. I tried to add interpreter_contraints to differents places but I'm not able to make that work. How can I force pants to use python3.9 when resolving dependencies for pants plugins?

Pants runs itself using the Python version selected by the

pants

script: plugins will need to work with the version selected there

my plugin is in the same repo so it has a BUILD file. It also have its own requirements target with its own resolve

by editing the

pants

script

like changing the shebang?

the

pants

script is written in bash: the one in your repo probably looks like this: https://github.com/pantsbuild/setup/blob/gh-pages/pants

I have my own script that ultimately pull the pex from github because of firewall and stuff

got it. then the PEX file is what is driving which interpreters are used.

So at the end of the day, I call the pants pex file. would it work if I call it with PYTHON=3.9?

PEX is a whole other story…. i’m actually not sure how to control which interpreter is used at runtime for a PEX (the constraints are baked in at build time)

ok then. It could be a bit problematic with plugins

PEX_PYTHON ?

looks like either:

PEX_PYTHON

or

PEX_PYTHON_PATH

ah, nice

sure thing