So, I have a python script I’d like to run from time to time from the CLI (on Linux) that resides inside a venv. What’s the recommended/intended way to do this?
Write a wrapper shell script and put it inside a $PATH-accessible directory that activates the virtual environment, runs the python script and deactivates the venv again? This seems a bit convoluted, but I can’t think of a better way.

      • Andy@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        4 days ago

        I use my own Zsh project (zpy) to manage venvs stored like ~/.local/share/venvs/HASH-OF-PROJECT-PATH/venv, so use zpy’s vpy function to launch a script with its associated Python executable ad-hoc, or add a full path shebang to the script with zpy’s vpyshebang function.

        vpy and vpyshebang in the docs

        If anyone else is a Zsh fan and has any questions, I’m more than happy to answer or demo.

    • Violet_McQuasional@feddit.uk
      link
      fedilink
      arrow-up
      2
      ·
      4 days ago

      This. I’ve experimented by using pex before and one or two other means of executable python wrappers and they suck. Just do as lakeeffect says.

  • gitamar@feddit.de
    link
    fedilink
    arrow-up
    3
    ·
    4 days ago

    I use pipenv with pyenv together. This works pretty well, also in cron jobs. Just add pipenv run python script.py to the cron table.

  • namingthingsiseasy@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    3 days ago

    Just in case this comment didn’t make it explicitly clear, you can just invoke the python binary inside your venv directly and it will automatically locate all the libraries that are installed in your virtual environment.

    To show how this works, you can look at the sys.path variable to see which paths python will search for modules when you run import statements. Try running python3 -c 'import sys; print(sys.path)' using your system python, and you will only see system python library paths. Then, try running it again after replacing python3 with the full path to the python3 binary in your venv, and you will see an additional entry in the output with the lib directory in your venv, which shows that python will also look there for modules when an import statement is executed.

  • santa@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    arrow-down
    3
    ·
    4 days ago

    Does it need access to anything local? If not, you could run it as an AWS Lambda on a schedule.