rapid-exabyte-76685
03/27/2022, 8:24 AMPIP_NO_BINARY
for a single dependency, via an override
key on poetry_requirements
etc? I'm currently developing on an M1 and there is currently an issue with the grpc package and the way its binary is shipped (see https://groups.google.com/g/grpc-io/c/9iM4SPpOyC8 for a great summary).rapid-exabyte-76685
03/27/2022, 8:45 AMPIP_NO_BINARY=grpcio ./pants <goal> <target>
seems to work either for me, whereas it does with pipenv
happy-kitchen-89482
03/28/2022, 5:55 AMhappy-kitchen-89482
03/28/2022, 5:56 AMrapid-exabyte-76685
03/28/2022, 6:20 AMrapid-exabyte-76685
03/28/2022, 6:23 AMpoetry_requirements
if this support was going to be landed in python_requirements
first.rapid-exabyte-76685
03/28/2022, 6:31 AMhundreds-father-404
03/28/2022, 2:55 PMpoetry_requirements(
overrides={"req": {"pip_options": ["--no-binary"]}},
)
happy-kitchen-89482
03/28/2022, 3:48 PMhappy-kitchen-89482
03/28/2022, 3:49 PM--no-binary
for just a single requirement?hundreds-father-404
03/28/2022, 5:50 PM--no-binary
targets into the same reqs.txthundreds-father-404
03/28/2022, 5:52 PMpython_requirement
targets; the input requirements.txt
is only to generate those targets. We never tell Pants -r my_reqs.txt
. And that's important so that inline targets & Poetry continue to work properly
I think the modeling must live on python_requirement
targets