Virtualenv's `bin/activate` is Doing It Wrong

gistfile1.md

This article is now published on my website: Prefer Subshells for Context.

forget pip - pip3
use conda https://conda.io/docs/_downloads/conda-cheatsheet.pdf

This is great. I would just note that there is no need to hard code the path of the virtualenv in shell and batch scripts. It can and should be relative.

Please also look at vrun [1] which is super lightweight and simply activates a virtualenv for the duration of a command. You run something like env/bin/vrun <cmd> and it is executed with all of the virtualenv scripts etc on the path. This is similar to vex but with fewer assumptions and should be mentioned in the same conversation.

[1] https://pypi.org/project/vrun/

Helpful! Thank you!!

404 on the link 👎

still 404

@nmaupu , @benedikt-bartscher: here is a copy of the page on the Wayback Machine from archive.org.