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.

  • Sigmatics@lemmy.caEnglish
    2·
    1 year ago

    It is quite telling that the one tool that covers most of the features expected from a packaging tool is one maintained by a single author: PDM.

    In my experience it has been a pleasure to use it as well, even though it is quite new.

  • stilgar [he/him] @infosec.pubEnglish
    1·
    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.devEnglish
      2·
      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.