Hi all, I’m wondering if there’s a equivalent for

poetry lock --no-update

when running

pants generate-lockfiles

Historically when adding a dependency (with poetry), I’d add the dep to the

pyproject.toml

and then run

poetry lock --no-update

to generate the new lockfile with my dep without updating the rest of the dependencies. Doing the same in pants:

pants generate-lockfiles

it seems to eagerly want to update all dependencies at once. Is my understanding here correct? How are people managing this?

your understanding is correct, there's some on going work in this area, such as: https://github.com/pantsbuild/pants/pull/20364

That’s great, thanks Andreas

and regarding your second question, there's a few ways I imagine would be common to manage this today, one being to update often (and pants is nice about telling you exactly what changes where made in your lockfiles), and the other is to use hard pins on dependencies you explicitly don't want to upgrade for at the moment (in the requirements.txt file).

@curved-television-6568 i know this has been dicussed to some detail - is there any plans a foot to generate a poety.lock from the pants lock files ? I did a cursory glance and it would seem that the pants lock files are a superset of the poetry ones. (poetry was missing some detail if I recall)

no such plans that I'm aware of, no.