> I don’t actually consider the Python ecosystem and its tooling to be "hot garbage". And in the same breath proceeds to describe Python ecosystem as hot garba

> I don’t actually consider the Python ecosystem and its tooling to be "hot garbage". And in the same breath proceeds to describe Python ecosystem as hot garbage, no quotation marks needed. Comeon, why do all these mental gymnastics trying to convince yourself your tools don't suck, when you already have all the evidence that they do? As for Rye itself: yeah, no. pyproject.toml was supposed to do that... Of course it didn't work. And so did plenty of other "solutions" (Pipenv? Poetry?) that try to work around the defective basic components instead of building from scratch. To fix this problem for real, the first stage needs to be the one where the people working on the fix understand the problem. As long as these people aren't willing to be honest with themselves and won't admit how bad their work has been so far, it's not going to get better. It will be more of the same band-aid.