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

13 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

[-] Fenzik@lemmy.ml 4 points 1 year ago* (last edited 1 year ago)

Worth noting the thing that conda does well is handle system-level dependencies, there are a lot more binaries available there (beyond just Python packages) that make it easier to install packages without having to compile C++ code or something.

Besides that I hate it haha, it makes everything else so complicated

I’ve also not had great experiences with poetry, it’s supposed to use the lock file to lock in dependencies but whenever I did anything the lock file was always being updated which kind of defeats the point. I’m sure it was user error but the fact that the lock file doesn’t stay static by default is already weird to me

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

It would be interesting to hear what you mean about the lock file being updated. Many Poetry commands should and do touch the lock, like poetry add or poetry update, but of course poetry installshould leave it untouched.