On Tue, Feb 11, 2025 at 10:01 AM Olaf Meeuwissen <olaf@???> wrote:
> I don't know why you want to avoid virtual environments

I'm not OP but I have experience trying to run python scripts from
crontab in various virtual environments and its ROUGH.

/bin/sh may or may not support the source command. You can run a
/bin/sh script to call a /bin/bash script to call the venv Python
script. Or set the SHELL env var in crontab if your local crontab
supports that (to run /bin/bash for all crontabs instead of /bin/sh)

pipenv won't run with a locale set and may or may not have weird PATH
issues. Or maybe it works now.

Why we have to deal with /bin/sh instead of just use bash everywhere
in 2025 is another good question, if I never see /bin/sh again I'll be
OK.

I wish there were a scripting language you could compile with static
linking, LOL.