then cites two examples where you have to write a couple extra args..

better title: “QOL changes i wish UV had”

Since uv needs a singular resolution that's entirely intentional. In npm you can install diverging resolutions for different parts of the tree but that is not an option with Python. I had to make the same decision in Rye and there is just no better solution here.

If an upper bound were to be supplied you would end up with trees that can no longer resolve in practice. Some package ecosystems in Python even went as far as publishing overrides for old packages that got published with assumed upper bounds that ended up wrong.

Don't forget that you cannot know today if your package is going to be compatible or incompatible with a not yet released package.