Hello! What is the guidance on telling Pants expli...
# general
s
Hello! What is the guidance on telling Pants explicitly to not use a dependency from source? For example, in my monorepo, projectA depends on projectB. In projectA's python_distribution target's dependencies field, I could specify projectB's python_distribution target. But what if I want to pin projectB to a previously released version? I tried to define a python_requirement target in projectA's BUILD with this pinned dependency, but in the resultant projectA.whl metadata, I see both projectB==<releasedversion> and projectB==<devversion>. Any ideas on how to avoid this?
h
Hmm, not sure there is an easy way to do this without writing a
setup.py
(or similar) manually
Currently the generated setup.py is kind of an all-or-nothing proposition, unfortunately
s
Thanks, Benjy. Is this a feature that is being worked on?
h
It is something I want to tackle in the new python backend, but that is a while out
gratitude thank you 1