Re:Virtualenv's bin/activate is Doing It Wrong
by tbatterii on Wednesday February 27, 2013 @08:55AM
(#5292332)
I haven't used activate in years, I just call the interpreter directly.
[ Parent
| on HN ]
Re:Virtualenv's bin/activate is Doing It Wrong
by thraxil on Wednesday February 27, 2013 @10:02AM
(#5292649)
Yep. I do mostly Django development and my project template just automatically sets up a virtualenv in a 've' subdirectory and sets the shebang line in manage.py to "#!ve/bin/python". From there, I just run "./manage.py whatever" and I never even have to think about it.
Re:Virtualenv's bin/activate is Doing It Wrong
by untothebreach on Wednesday February 27, 2013 @10:53AM
(#5292949)
that's a good way...since I already use Makefiles to do little tasks in my projects, I end up just setting `PYTHON=.virtualenv/bin/python` and in my targets, using `$(PYTHON)` instead of `python`. Ditto for `pip`, `nosetests`, etc.