I don't disagree, but the trouble is, which do you axe?
Everyone agrees there's too many, but nobody yet agrees what to converge on.
It's probably made worse by the fact that package management isn't considered part of the python core team's remit.
There's a github issue on the Rye page for "Should Rye exist?" for exactly that reason, and Armin (the original developer) seems pretty consious of the package manager clutter. But in all honesty, it solves a real problen that exists (that other package managers don't solve) so I can't see any reason Rye should do anything differently just because there are lots of package managers that currently exist.
Everyone agrees there's too many, but nobody yet agrees what to converge on.
It's probably made worse by the fact that package management isn't considered part of the python core team's remit.
There's a github issue on the Rye page for "Should Rye exist?" for exactly that reason, and Armin (the original developer) seems pretty consious of the package manager clutter. But in all honesty, it solves a real problen that exists (that other package managers don't solve) so I can't see any reason Rye should do anything differently just because there are lots of package managers that currently exist.