4 ms·
Yeah I think for me it's more about the intellectual overhead than performance. With this you just have one tool, and it's just easier for me to understand wha
by ehremo 11y ago
Yeah I think for me it's more about the intellectual overhead than performance.
With this you just have one tool, and it's just easier for me to understand what's going on compared with virtualenv.
- Galanwe 11y agoVirtualenv 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.
- mbreese 11y agoIt 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...
- deckiedan 11y agoWhat 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/ http://streetsign.org.uk/ [2] https://bitbucket.org/dfairhead/streetsign-server/src/5b359a4b423c56e1cab2923ac307223a534a80e2/setup.sh?at=master https://bitbucket.org/dfairhead/streetsign-server/src/5b359a...
- bpicolo 11y agohttp://nuitka.net/ http://nuitka.net/
- mbreese 11y agoDoes that work with Cython compiled dependencies?
- perlgeek 11y agoYou can build debian packages that way; dh-virtualenv (https://github.com/spotify/dh-virtualenv https://github.com/spotify/dh-virtualenv) makes it quite easy to pack a full virtualenv into a .deb.