@carlton Some of my Ruby and Node friends feel Python's package management will never be adequate if this problem isn't addressed.

Assuming you don't mean multiple versions of the same package available everywhere but instead one per package, I think we'd basically need a separate site-packages directory location per package for this. 😬

@treyhunner Yeah, I have no grand solution waiting up my sleeve. Greater minds than mine can solve the how. 🥳

It’s frustrating when all dependencies (and the project) have to be on the same compatible ranges. A slow updating package blocks everyone else updating even if its usage of the target package are entirely internal.

🤷

@carlton @treyhunner To your last point, this is why we are still stuck on Python 3.12 for more projects that I care to admit to.

Since we can't stop authors from pinning to upper boundaries, I wish we had the mechanics to at least say, "IGNORE THIS" very loudly so we can move around it.