How to improve Python packaging, or why fourteen tools are at least twelve too many (chriswarrick.com)

submitted 1 year ago* (last edited 1 year ago) by oscar@programming.dev to c/python@programming.dev

2 comments fedilink hide all child comments

I stumbled upon this while researching package management options for python, and found it a really interesting read.

I like python as a language but this mess is something that needs to be addressed for me to consider python for future projects. I can't imagine how confusing it must be for new users.

you are viewing a single comment's thread
view the rest of the comments

[-] stilgar@infosec.pub 1 points 1 year ago

Our organisation has gone all in on Poetry, no regrets so far. The UX and dlscoverability is just so much better than the other options.

I do look jealously at languages that have great official tools like go and cargo though.

[-] Blackthorn@programming.dev 2 points 1 year ago

I love cargo, but cargo.io could REALLY make good use of namespaces. It's insane when clear library names are taken by highschoolers at their first project and there is nothing to be done about it. I'd also like some kind of curating on the packages.