Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Beginners Guide : pip and virtualenv

mahdiyusuf.com

Post reply on HN
Print view View original

11–15 of 15 posts

Re: Beginners Guide : pip and virtualenv

#11

Post by izak30 »

2mur wrote: post #10

Nice article. I use virtualenv heavily and still do the symlinking dance. I keep my django trunk in a ~/libraries folder and symlink the django folder to the /path/to/virtualenv/lib/pythonX.X/site-packages folder. I'm not sure that I have a compelling reason for doing so.

cd ~Path/to/django; pip install -e .;

It feels better than symlinking to me.

I would really only do this if I had a custom patched django though. If speed/bandwidth is a concern, just make sure your pip cache is setup properly.

Re: Beginners Guide : pip and virtualenv

#12

Post by myusuf3 »

2mur wrote: post #10

Nice article. I use virtualenv heavily and still do the symlinking dance. I keep my django trunk in a ~/libraries folder and symlink the django folder to the /path/to/virtualenv/lib/pythonX.X/site-packages folder. I'm not sure that I have a compelling reason for doing so.

I would suggest to stop doing that since thats the point of virtualenv; it is a bit of pain since it doesn't put django-admin.py in path but you can always refer to it.

Re: Beginners Guide : pip and virtualenv

#13

Post by myusuf3 »

pdubroy wrote: post #9
Pewpewarrows wrote: post #8

Earlier quoted context omitted.

Except for when you DO want to install a package globally. Utilities like pyflakes and fabric, for example.

On my personal machines (effectively single-user), I find there's no need to install packages globally. I have a default virtual environment that I activate in my .profile, and anything that's not project-specific gets installed there. Not saying everyone should do this, but it works well for me.

thats such a hassle. though, why dont you just install global requirements in the base machine, you wont always have to keep turning on virtualenvs.

Re: Beginners Guide : pip and virtualenv

#14

Post by myusuf3 »

antrix wrote: post #6
stock_toaster wrote: post #4

Earlier quoted context omitted.

I liked virtualenvwrapper, but it added considerable (noticable) latency to my terminal startups. I ended up removing it and went back to manual virtualenv activation (with a couple of small helper bash functions of course).

Same here. At times, it gets so bad that I have to hit Ctrl+C and then it dumps out a nice big trace before giving me my shell prompt.

I have never seen that. it just loads a script into path. interesting.
Post reply on HN