Poetry continues its reputation as "the package manager that will tell you what you're doing is wrong and bad and you should feel bad for wanting to do very obvious things like show a diff of what was updated when you regenerate the lockfile"

https://github.com/python-poetry/poetry/issues/9259#issuecomment-2030668775

Add `poetry lock --diff` flag to show which packages were changed when locking · Issue #9259 · python-poetry/poetry

Issue Kind Brand new capability Description first of all THANKS to all y'all, really appreciate all the work that has gone into poetry, we use it all the time and love it. We have made an action to...

GitHub

It's fine to be an "opinionated package" but like when your entire issue triage process is just to be super rude to everyone until nobody wants to raise issues then maybe it's you who is doing something wrong.

also like, as someone who has fought through trying to make a contribution, this is hands down the package most direly in need of any kind of developer documentation i've ever seen - like if y'all are so stressed about adding a print statement maybe you should wonder why something with 33 million monthly downloads only has 14 people with >=10 commits in the repo.

y'all, don't use poetry. it became my default when it was the only tool of its kind, but it's not anymore, and it's actually missing some pretty core features that other tools have out of the developer's eternal belief that they are the smartest ones in the room (and how it's totally impossible to contribute for technical and social reasons). These people are pricks and i'm out.
Update: one person who I dont care for and one normal person. Revising my "do not use" to "use with caution and consider other tools"
@jonny holy fucking shit, though, I just read through the rest of the issue and goddamn that one dev is an asshole.

"you can lead a horse to water" motherfucker _you're_ the horse here, refusing to read a goddamn thing that was written

Jesus, I hate dealing with people like that. Like beating your head against a wall.
@jonny recommendations for an alternative? pdm? poetry just recently got me to a more productive place in my very auto-didact Python journey, I would be missing it. But if they are behaving as you say, they are setting themselves up for stagnation in the long run, so that would be a reason not to build tooling around it I guess.
@jonny i guess the “opinionated” in software context means “the authors have a very high opinion of themselves”…
@jonny Dangerous Use of Simply
@arrjay
It was literally an issue about how complicated it is to keep the lockfile in sync!!!!!!!!!!!!!
@jonny I especially like that it starts with “you’re misunderstanding something but we don’t know what”. Good, great.
@aud and then proceed to totally not understand what i'm talking about lmao
@jonny if `poetry.lock` is checked in, how about writing a diff tool that summarises the changes? That would come in handy, e.g. folks could plug it into their `on: pull-request` pipeline to highlight the changes at the pr review stage. Kinda similar how js can be unuglified or compiled translation file or image files. WDYT?

@dimaqq that's what I did!
https://github.com/linkml/linkml/pull/2044
which makes this
https://github.com/sneakers-the-rat/linkml/pull/6

(and one like comically rude poetry dev is telling me is pointless and i should feel bad about needing to work around a pretty obvious and easy missing feature in their cli tool)
https://github.com/python-poetry/poetry/issues/9259#issuecomment-2031238318

"the whole premise for this feature request and that other pull request collapses"

lmao

Automatically PR to update poetry lockfile v3 by sneakers-the-rat · Pull Request #2044 · linkml/linkml

Continues: #2028 Continues: #2023 OK I AM SO SORRY this has taken several PRs to get right - hopefully it's clear that i am not trying to be sloppy and these are problems caused by CI being weird a...

GitHub
@jonny I'm so sorry, I think that you misunderstood me. I was trying to propose that a separate, standalone utility and a github action could be made that shows lock file diffs. So that other developers can pull it into their PR workflows. In my mind, it would parse the lock file, rather than rely on `poetry show -t`. Arguably this could be generalised to other lock files: pdm/pip, npm/yarn, rust/go, etc. Perhaps it already exists!
@dimaqq
Well, I guess thats what I have proposed and drafted in that issue, we'll see if they go for it. Idk about different lockfile formats, theyre all sorta different, but its ultimately not more complicated than comparing added, removed, changed versions so ha could probably be done