Hi, I'm playing around with

experimental_shell_command

to generate c++ extensions using cmake and pybind11 for python, the build file I'm using right now:

shell_sources(name="build-c-exts", sources=["./**/*"])

experimental_shell_command(
  name="c-deps",
  command="./build.sh",
  log_output=True,
  tools=["make", "cmake", "cat", "bash", "env", "chmod", "gcc", "g++", "as", "ld"],
  dependencies=[":build-c-exts"],
  outputs=["results/", "logs/my-script.log"],
)

But I get an error that it can't find

Python.h

(I'm using pyenv), error in the thread ⬇️

Hello! Is this working when not using Pants? It's plausible this is an issue w/ Pants not setting up the correct environment variables because it tries stripping things. But another hypothesis is missing certain system dependencies like

python3-dev

yes, it works when not using pants. And it's definitely because

python3-dev

is missing from the system^^, adding it works Here the expected behavior I think is to use pyenv to find the python headers ?

adding it works

Adding it how so? Installing via

apt-get

for example? Adding to

tools=[]

?

installing via apt-get

Cool

Here the expected behavior I think is to uses pyenv to find the python headers ?

Perhaps Pants is using a different interpreter than what you use when running directly? Is your

build.sh

doing the Python interpreter selection for you? (Altho does it even call Python directly?)

it doesn't call python directly but runs a cmake build

the

env

and

PATH

will be highly filtered in the script, so my guess is that a particular variable you’re expecting is not present

To determine that's it's an issue, you could try running

env

in your terminal to see all your env vars. Then try running that same script directly w/o Pants where you set the env vars to empty values like

CPPFLAGS=''

for example. Might be hard to reproduce now that you installed

python3-dev

tho

if you determine that that is the problem, would you mind opening a Github issue about it?

yes, it's definitely worth adding ^^, but I don't think it's the problem here It was simply that pants was using my

<PATH>

python instead of

<PYENV>

since I defined both in the config. On a similar note, about the experimental_run_shell_command, does it support pass through args ? I'm trying to create a command that add a poetry dep and updates the constraints.txt file

./pants run  poetry:add -- requests tqdm

and will be passed to the

poetry/add.sh

script as classic sh arg vars

On a similar note, about the experimental_run_shell_command, does it support pass through args ?

I’m trying to create a command that add a poetry dep and updates the constraints.txt file

if it doesn’t, it should. lemme see.