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

18 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 9 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.

[-] roze_sha@programming.dev 3 points 1 year ago

There are tools like Huak and Rye in development.

[-] Spott@lemmy.world 9 points 1 year ago

The value of cargo and go tools doesn’t come from the all-in-one nature of them, it comes from the official nature of them.

If something doesn’t work with cargo, it is a bug. Period. There isn’t any “it works with pip” back and forth arguing over whose fault it actually is (package? Or poetry/pipenv/pip-tools/conda/etc? This happened with pytorch a while ago, and I’m not sure if poetry and pytorch get along even now)

There also isn’t any debate over project files or configuration stuff — Pyproject.toml vs setup.cfg vs random dot files in the project directory — if you are a currently developed project you support whatever cargo supports and you move to support the latest format rather than dragging your feet for years (pyproject.toml has been the “next thing” for python since 2016! And is only finally getting widespread support now… 7 years later).