@theorytoe
I agree, this IS annoying, but man, come on, using venv isn't complicated at all:
python3 -m venv .
./bin/activate.sh
pip3 install some_shit
You can then use this dir and move it around (mostly) without worrying about system-wide python getting upgraded.
Besides, you can always force it to install modules user- or system-wide and have leftovers in site-packages — which was kinda annoying too.
@m0xee running shit on a venv is fucking HELL
Follow
@theorytoe
Why? I even run shit in venv from runit with no issues.
Just source the activate script first: ". bin/activate", then "exec python3 whatever.py" — you're all set!
i have never had a good time with it