• monogram@feddit.nl
      link
      fedilink
      English
      arrow-up
      8
      ·
      11 hours ago

      pipx, poetry, pipsi, fades, pae, pactivate, pyenv, virtualenv, pipenv

      Let’s hope this next one will be the true standard.

        • dallen@programming.dev
          link
          fedilink
          arrow-up
          3
          ·
          8 hours ago

          I’ve been mostly a poetry guy but have tested out uv a bit lately. Two main advantages I see are being able to install Python (I relied on pyenv before) and it’s waaay faster at solving/installing dependencies.

          • sugar_in_your_tea@sh.itjust.works
            link
            fedilink
            arrow-up
            1
            ·
            7 hours ago

            Yeah, it certainly looks nice, but my problems are:

            • everything runs in a docker container locally, so I don’t think the caching is going to be a huge win
            • we have a half-dozen teams and a dozen repositories or so, across three time zones, so big changes require a fair amount of effort
            • we just got through porting to poetry to split into dependency groups, and going back to not having that is a tough sell

            So for me, it needs to at least have feature parity w/ poetry to seriously consider.

            • Eager Eagle@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              5 hours ago

              uv is still faster with a cold cache

              and uv does have dep groups

              about the second problem, there’s an issue open on writing a migration guide, but migrating manually is not too difficult.