News for hackers. Stuff that matters.
Re:Uv is fantastic, but its package management UX is a mess by __mharrison__ on Thursday May 21, 2026 @10:24PM (#48231245)
I'm curious. Do you have real world examples of when you want to do this?
Re:Uv is fantastic, but its package management UX is a mess by gbear605 on Thursday May 21, 2026 @11:07PM (#48231513)
This is Java, but recently I had a case where one library depended on a version of an Apache Commons library, and another library depended on a different version of the same Apache Commons library, and neither version worked with both libraries. In my case, I was able to upgrade one of them to a newer version so that I could use just one Apache Commons version, but I got lucky there.
Re:Uv is fantastic, but its package management UX is a mess by deathanatos on Friday May 22, 2026 @12:22AM (#48231892)
The monolith I work on has this dependency chain:

  monolith -> openai
  monolith -> langchain-openai -> openai
openai, thus, is both a direct and indirect dependency. langchain-openai recently had a vulnerability, and the patch fix is only after a major upgrade to openai. Thus, to upgrade langchain-openai here, I also need to upgrade monolith's use of openai. (From v1 to v2.)