Getting some issues installing

lxml

when running

pants generate-lockfiles

. Same

pyproject.toml

with a normal venv installs successfully. What do I need to do? Exposed development headers in my shell. Is there a more hermetic way to do this?

An option to consider would be prebuilding the appropriate version(s) of the library into appropriate wheels for your platform outside of pants, and have pants consume those wheels, rather than needing pants to do the building internally. That's not "perfect" though. (https://www.pantsbuild.org/2.19/reference/subsystems/python-repos#find_links is one way to approach this.) Potentially https://www.pantsbuild.org/2.19/reference/subsystems/python-native-code is relevant too, but that's kinda just a dedicated way to escape the hermeticity. I don't think there's an "easy" way to build wheels hermetically with pants targets etc. providing whatever external libraries are required.

I see. I'm guessing I could also write rules for the native library dependent packages and provide them as

file://

to find links maybe? Not sure if I could reference artifacts like that