Re:Pip -t: A simple and transparent alternative to virtualen...
by Galanwe on Thursday June 25, 2015 @01:49PM
(#9779622)
Virtualenv is really not complicated. I think your time would be better spent learning how it works than just hacking some crappy workarounds to skip the problem.
[ Parent
| on HN ]
Re:Pip -t: A simple and transparent alternative to virtualen...
by mbreese on Thursday June 25, 2015 @02:28PM
(#9779944)
It can be a pain when trying to distribute software to users (non-python programmers). What I usually end up having to do is distribute virtualenv with my code, and include a simple Makefile/build script to setup the venv. Invariably someone tries to then move that directory and everything ends up getting screwed up until I can tell them to run "make clean all".
I'm not too sure that this would end up being any easier, but maybe...
Re:Pip -t: A simple and transparent alternative to virtualen...
by deckiedan on Thursday June 25, 2015 @03:25PM
(#9780328)
What I'm doing with streetsign[1] is including a download virtualenv step in the setup script[2]. The virtualenv gets set up in `.virtualenv/`, so most users won't even see it.
[1] http://streetsign.org.uk/ [2] https://bitbucket.org/dfairhead/streetsign-server/src/5b359a...
Re:Pip -t: A simple and transparent alternative to virtualen...
by perlgeek on Friday June 26, 2015 @12:23PM
(#9785733)
You can build debian packages that way; dh-virtualenv (https://github.com/spotify/dh-virtualenv) makes it quite easy to pack a full virtualenv into a .deb.