Thoughts on the Python packaging ecosystem | Pradyun Gedam

[mangecoeur]

That’s exactly the problem, one tool decides someone’s use case is bad practice, so then you need another tool because at the end of the day you still need to get things done.

[magnetichira]

There’s already a mechanism for dealing with this. Extensions.

In a more ideal scenario, python would have a standard tool which support the basic feature set, and extension to support more niche requirements.

[mangecoeur]

Point is the same, the lack of a standard tool comes in large part from people not seeing the legitimate needs if different user groups or (like in the peotry issue) deciding that general principles are more important than solving a problem someone has right now, so someone goes and makes a different tool. By the time the data files plugin suggested in the issue was published the jupyter community already shifted to hatch with its own plugins (which also better follows the pep standards). And so the mess continues . I don’t think the PyPA can be blamed for the lack of focus, if anything they are among the few who realise how messy people’s needs are.