How to improve Python packaging, or why fourteen tools are at least tw
chriswarrick.com
A journey to the world of Python packaging, a visit to the competition, a hopeful look at the future, and highlights from a disappointing discussion.

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.

  • @coffeewithalex@lemmy.worldEnglish
    10•10 months ago

    It’s worth noting that there are basically just 3 systems worth considering, maybe even just 2.

    pip is usually part of the python distribution, so any lightweight project can be finished in 1-5 minutes with pip. It’s also quite widespread and the vast majority of publishers (if not all) target pip compatibility.

    Poetry is a great project management framework and it deals with dependency management beautifully. If you’re doing any data engineering or backend development, for any project that has more than 1 dependency and 200 lines of code, then Poetry is probably the best tool to use. Poetry makes the whole mess with helper tools like pip-tools seem outdated.

    Conda is for the crazy world of data science libraries where developers don’t bother with compatibility too much. Conda does it for them. And the users of those libraries can benefit from using conda.

    I think the big competition is between poetry and pip. Maybe one day poetry will come as part of some Python distributions.

    • @Fenzik@lemmy.mlEnglish
      4•10 months 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 [he/him] English
        2•10 months 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.

        • @Fenzik@lemmy.mlEnglish
          2•10 months ago

          But if I want to add a single new dependency, then I probably don’t want all the rest updated at the same time

          • @coffeewithalex@lemmy.worldEnglish
            2•10 months ago

            That can’t be achieved due to dependency compatibility. What if you installed y==1.4, and froze it for a while, and then you install x==3.2, and it depends on y==1.5 or later?

            pyproject.toml defines dependency restrictions, so it will be in accordance with that, but the lock file will change every time you add/remove dependencies. Naturally.

            • @Fenzik@lemmy.mlEnglish
              1•10 months ago

              I don’t find that behaviour natural unless there is a hard conflict or I request it. So I guess it’s just a philosophical difference that led me to having a bad tint with it.

              • @qwop@programming.devEnglish
                3•10 months ago

                If you use poetry add it should only update what is necessary, and you can use poetry lock --no-update to lock without updating everything.