[edfletcher_t137]

I included it because the author did, and irked me by openly admitting they recognize the argument but went against it anyway. There is good reason that particular XKCD hits so hard.

Chris Warrick has done a ton of thinking - and a lot of writing [1] - on the subject and has very sage things to say about it. But unlike the author, he didn't decide to write another one. Because there are many good reasons not to. Thanks for letting me know you didn't bother reading that follow-up though: pretty clear who is providing zero value here :shrug:

[1] In fact, here's more he has to say about it: https://chriswarrick.com/blog/2024/01/15/python-packaging-on...

[the_mitsuhiko]

I'm not entirely sure what you're suggesting other than "accept the terrible status quo". For what it's worth my personal use of rye predates the release by multiple years (not in this particular manifestation) and I held off releasing it for a very long time.

[edfletcher_t137]

> The PyPA should shut down or merge some duplicate projects, and work with the community (including maintainers of non-PyPA projects) to build One True Packaging Tool. To make things easier. To avoid writing code that does largely the same thing 5 times. To make sure thousands of projects don’t depend on tools with a bus factor of 1 or 2.

-- https://chriswarrick.com/blog/2024/01/15/python-packaging-on...

[the_mitsuhiko]

I mean, I can also try to tell the PyPA to do a thing or two but that won't magically make it work. The PyPA is a bunch of separate individuals doing their thing and they are free to listen to people or ignore them. I do not have the power (nor do I believe I should) to force them to do a specific thing.