• Iced Raktajino@startrek.website
    link
    fedilink
    arrow-up
    7
    ·
    2 days ago

    For me, it’s the rigid and wonky virtual environments. I get why they’re useful and necessary, but they’re awkward to use. Like, Node just works from the working directory with no fuss and python has to be all source {venv}/bin/activate and lord help you if you need to move it.

    Plus, I have never liked that the spacing is load-bearing.

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

      uv mostly gets rid of the “venv activation” thing (mostly bc you can still use it if you really want, but you don’t need to), you can do uv run main.py and it’ll just work, no need to even install packages explicitly, it’ll also do that for you and make sure your uv.lock is in sync with your environment.

      it’s the most hassle-free experience I’ve had with python, by a long shot.

      • Iced Raktajino@startrek.website
        link
        fedilink
        arrow-up
        4
        ·
        2 days ago

        Sounds like at least a minor improvement. Can those me moved and still work? Like, if I move the project folder, do I have to reinitialize it and download all the packages again?

        • WhyJiffie@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          21 hours ago

          you can always keep the venv dir in the project dir, even without uv. that’s what I do most of the times

        • Eager Eagle@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 days ago

          ah, it’s a massive improvement. Everything is in your project dir, so you can move it around. But uv is the fastest package manager, so reinstalling most things doesn’t take time; with the exception of dependencies that need to compile code in different langs.