• infeeeee@lemm.ee
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    edit-2
    1 year ago

    My workflow:

    cd project
    python -m venv .venv
    . ./.venv/bin/activate
    pip install -e .
    

    By default pyvenv excludes system packages, so I can have different versions in the venv. To reset the venv, I just have to delete the .venv dir.

    • Oscar@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I’ve been using pipenv for a good while but I’ve started to move over to venv slowly, and I like it so far. It’s a bit more of manual work but I feel like it’s worth it.

      • infeeeee@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        I love this workflow because it has only two prerequisites: python and pip. It works on windows, linux, any vm or container. Pipenv requires some setup, while this should work everywhere. In powershell you have to use ./.venv/bin/acticate.ps1 but that’s the only difference.

      • Mikina@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        What did you not like on pipenv in comparison to venv? I was always avoiding venv because it was, as you said, manual work and it was too much effort to again google what was the order of commands and parameters to start a venv, which is not an issue in pipenv, since you just pipenv install what you need.

        • Oscar@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          We had some issues in our CI where pipenv would sometimes fail to sync. It has recently gotten better, I think due to a fix of some race condition due to parallel installation. I think venv would be better suited for CI in general, since it allows the use of a simple requirements.txt file.

          The other thing is I think it is rather slow, at least on windows which most of my team uses.

          To conclude, I think as long as you aren’t having any trouble and it simplifies your environment, you might as well use it.

          • Mikina@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            I only use python as a go-to scripting language when I need to quickly automate something or write a quick throwaway script that requires an SDK, since there’s a python library for almost anything and doing it in powershell would be too much aditional work. But it does make sense that for CI you only need to figure out the venv setup once and you’re done, so it may be a better solution.

  • dukk@programming.dev
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    Thank god for NixOS. (My daily on my laptop, seriously flakes + nix-direnv is godsend for productivity. Reliable development environments and I don’t have to lift a finger!)

    • haruki@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Do you have any troubles running it as your daily OS? Do you use it as your hobby or also for your work?

      I know Nix and use it as my package manager, but I’m not sure about the experience with NixOS. So I’m still reluctant to make the switch.

      • dukk@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I just jumped in headfirst. I love it. It’s really just Nix, but with options to configure your whole system to your liking.

        Stability’s been rock-solid and I haven’t yet encountered anything truly headache-inducing.

        Here’s some starter advice:

        • Try to start with flakes. Nix channels are known for being…unreliable at times.
        • Start small, slowly extend. Many people’s Nix configs are often insanely abstracted and modularized. Personally, I started my flake config by installing KDE + Nix, and then linking the configuration.nix to the flake. (Remember, flakes just package the config, they’re not responsible for configuring the system).

        My Nix config is relatively basic (check it out here, so feel free to look around trying to understand it. I’d also suggest using Home Manger if you aren’t already.

        The NixOS forums are great for getting help. I’ll also point you towards the Catppuccin Discord server, the NixOS thread there is filled with many helpful people who helped me get started. (If you decide to swallow the Nix pill, feel free to join and ping me(my username’s Dukk); I’ll add you to the Nix thread).

  • Mikina@programming.dev
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I’ve recently discovered pipenv, and it has been a massive QoL improvement. No need to figure out bazillion of commands just to create or start an environment, or deal with what params should you use for it like you do with venv. You just pipenv install -r requirements.txt, and everything is handled for you. And when you need to run it, just pipenv run python script.py and you are good to go.

    The best thing however are the .pipfiles, that can be distributed instead of requirements.txt, and I don’t get why it’s not more common. It’s basically requirements, but directly for pipenv, so you don’t need to install anything and just pipenv run from the same folder.

    • HarryEffingPotter@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      Yessssss

      I actually wrote a script to make a folder an instant pipenv environment for me. Add it to your ./.zshrc. Has saved me a ton of time, I just removed some spaghetti lines that would reinstall pip and shit because it’s when I was still early days into Py dev, now I work more with Py than I do C# and I’m a senior C# engineer, I just enjoy the masochism of py.

      Also added a check for Arch/Ubu.

      # Automated python virtual environment.
      #######################################
      VENV(){
      if ! [ -x "$(command -v pipenv)" ]; then
           echo "pipenv not installed... installing it now!"
           sudo pip install pipenv
           OS="$( ( lsb_release -ds || cat /etc/*release || uname -om ) 2>/dev/null | head -n1 )"
           if [[ "$OS" == *"buntu"* ]]; then
              sudo apt install pipenv -y
           elif  [[ "$OS" == *"rch"* ]];  then
              sudo pacman -S pipenv
           fi
           pip install pipenv --upgrade
           echo "Installation complete!"
      fi
      if [ -n "$1" ]; then
              echo -e "Args detected, specifically using version $1 of python in this project!"
              version="$1"
      else
              version=$(python -V)
              version=$(echo "$version" | sed -e 's/Python //')
              if [ -z "$version" ]; then
                      version=$(python3 -V)
                      if [ -z "$version" ]; then
                               echo "No python version installed... exiting."
                               return
                      fi
              fi
      fi
      echo -e "\n===========\nCreate a Python $version virtual environment in $PWD/.venv [y/n]?\n==========="
      read -r answer
      case $answer in
          [yY][eE][sS]|[yY])
      export PIPENV_VENV_IN_PROJECT=1
      pipenv --python "$version"
      pipenv install -r ./requirements.txt
      echo -e "\n\n\nVirtual python environment successfully created @ $PWD/.venv!\n"
      echo -e "To run commands from this dir use 'pipenv run python ./main.py'"
      echo -e "To enter a shell in this venv use 'pipenv shell'."
      echo -e "To install from a requirements text file use 'pipenv install -r requirements.txt'"
      echo -e "To update pip + all pip modules use 'pipenv update'!\n"
      echo -e "Additional information can be found @ https://pipenv-fork.readthedocs.io/en/latest/basics.html"
      ;;
          [nN][oO]|[nN])
              echo "Fine then weirdo why did you run the command then, jeez.Exiting"
      ;;
       *)
       echo "Invalid input..."
       ;;
       esac
      }
      
    • wyrmroot@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I could redraw this whole chart using only references to pipenv based on my experiences with managing it alongside other tools (especially homebrew). It’s good at many things but is no magic bullet.

  • jerry@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    This Helen’s on my laptop from following AI install scripts. I high key hate Python, it’s my hated language and I wish another language was the default for ML.

  • leviosa@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Hopefully Mojo will sort it all out. Maybe even inspiring a new, positive streak of xkcd strips in the future?