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.

  • @logging_strict
    1•5 days ago

    The multiple venv for different Python versions sounds exactly like what tox does

    Then setup a github action that does nightly builds. Which will catch issues caused by changes that only tested against one python version or on one platform

    py313 is a good version to test against cuz there were many modules removed or depreciated or APIs changed

    good luck. Hope some of my advice is helpful

    • @Andy
      1•4 days ago

      Thanks, yes, I use nox and github actions for automated environments and testing in my own projects, and tox instead of nox when it’s someone else’s project. But for ad hoc, local and interactive multiple environments, I don’t.