> everybody else was blaming themselves for a problem and didn't have a clear understanding of what was wrong with pip or what a correct model for managing python dependencies is (short answer: see maven)
I always looked down on the Java ecosystem but if it turns out Maven had a better story all along and we all overlooked it, that's wild.
Maven has its own bone headed design where it SILENTLY resolves conflicting dependency branches through a “closest to dep tree root wins” rule.