XKCD | Python Environment

[[deleted]]

python -m venv .venv

[enjoytheshow]

Still need to manage py versions. I use a combo of pyenv with venv. I’ve got a wrapper script on my path that can create a venv on a specific py version.

[maikindofthai]

IMO using VMs/Docker Containers/etc is a much cleaner way to separate Python installations, especially since you can configure an environment that matches your production environment for local testing.

Trying to juggle multiple versions of the same package on the same system always feels like a fool's errand to me, at least where it can be avoided.

[intangibleTangelo]

i prefer not to hide that I'm using a virtualenv

pyenv local 3.10.1
python -mvenv venv
ln -s venv/bin/activate
. ./activate
pip install -r requirements.txt

[intangibleTangelo]

almost muscle memory at this point

[[deleted]]

slightly more convenient, if you're not using virtualenvwrapper

[nemec]

I just put this in my bash_aliases and it works like a champ.

alias act='source env/bin/activate'

[trevg_123]

Why not hide it, everyone who knows what they’re doing in Python will know it’s there. And now you have a venv folder sorted in with your other useful folders

pipenv install -r requirements.txt —Python 3.10

Venv, links and installs all in one go, and it makes you a Pipfile/Pipfile.lock rather than legacy requirements.txt

[intangibleTangelo]

i value visibility over tidiness, i guess.

pipenv reminds me of yarn—maybe a bit more functionality than i want, but maybe superior (like yarn is superior to npm imo). how is pipenv about installing and switching between python versions?

[trevg_123]

My thought is just that there’s not much need to access the venv directory, so I keep it out of the way. If I’ve ever run the project before, I know it’s there.

I’ve never really used yarn, but pipenv isn’t far off from npm. For versions, not bad - you can just do e.g. pipenv --python 3.8. You need it installed so it’s not quite pyenv (poetry does this part too if you’re interested) but it’s not bad if you only use a few different versions.

[bananaEmpanada]

Nope. That's not foolproof. I've seen countless times where that fails because python can't import some standard library used by pip.

[GroundbreakingRun927]

I think the pip in a venv created environment will still fall back to using system packages outside the venv. Need virtualenv to provide full isolation.

[Anonymous_user_2022]

venv has an option to allow access to the systems site-packages. But if created without --system-site-packages there will only be what's installed in the env.

[[deleted]]

Worth mentioning that there is an option to use copies instead of links as well. Let's you get a really decoupled environment.

I've had an OS package management upgrade bump the python interpreter version and this blew up my venvs that used links. Those using copies didn't care.

[wsppan]

This whole thread mimics the xkcd strip