4 ms·
Why I love virtualenv and pip. We use virtualenv and pip extensively here, with virtualenvwrapper. mkvirtualenv <project> workon <project> pip install -
by kevcampb 13y ago
Why I love virtualenv and pip.
We use virtualenv and pip extensively here, with virtualenvwrapper.
mkvirtualenv <project>
workon <project>
pip install -r requirements.txt
It just works. I don't spend any time on it. Our developers don't have any problems with it. All the other considerations in the article we either handle as you're meant to, or understand the limitations.
Still, looking forward to some interesting comments on here.
- yukkurishite 13y agoThanks for your pointless blog post
- shintoist 13y agoThanks for your pointless comment
- jvdh 13y agoDid you actually read the entire article, or did you just come here to say that?
- Anderkent 13y agoIt extends to deployment. Off top of my head, the script that you have to write to trivially deploy with virtualenv is something like: virtualenv --no-site-packages -p$PYTHON $workdir "$workdir/bin/activate" (cd $my-package-dir && python setup.py) "$workdir/bin/deactivate" virtualenv --relocatable "$workdir" fpm -s dir -t deb -n "$package" -p "$package.deb" -d <system dependencies> ... And you have a deb that you can just scp anywhere and it'll just work.