News for hackers. Stuff that matters.
Re:Beginners Guide : pip and virtualenv by flexterra on Sunday August 07, 2011 @01:02AM (#2855814)
You should try virtualenvwrapper, it makes the process of activating and changing between virtualenvs a breeze.
Re:Beginners Guide : pip and virtualenv by stock_toaster on Sunday August 07, 2011 @03:24AM (#2856084)
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).
Re:Beginners Guide : pip and virtualenv by antrix on Sunday August 07, 2011 @04:30AM (#2856189)
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.
Re:Beginners Guide : pip and virtualenv by myusuf3 on Sunday August 07, 2011 @11:34AM (#2856813)
I have never seen that. it just loads a script into path. interesting.
Re:Beginners Guide : pip and virtualenv by myusuf3 on Sunday August 07, 2011 @01:04AM (#2855818)
upcoming post :P
Re:Beginners Guide : pip and virtualenv by 2mur on Sunday August 07, 2011 @09:04AM (#2856525)
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.

Re:Beginners Guide : pip and virtualenv by izak30 on Sunday August 07, 2011 @11:24AM (#2856781)
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 by myusuf3 on Sunday August 07, 2011 @11:32AM (#2856804)
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 by pdubroy on Sunday August 07, 2011 @08:21AM (#2856484)
One of the nice things about virtualenv is that it installs a copy of pip into every virtual environment you create. If you always have one of the environments active, there's no need to even install pip globally.
Re:Beginners Guide : pip and virtualenv by Pewpewarrows on Sunday August 07, 2011 @08:33AM (#2856495)
Except for when you DO want to install a package globally. Utilities like pyflakes and fabric, for example.
Re:Beginners Guide : pip and virtualenv by pdubroy on Sunday August 07, 2011 @08:42AM (#2856501)
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.

Re:Beginners Guide : pip and virtualenv by myusuf3 on Sunday August 07, 2011 @11:34AM (#2856811)
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 by pyre on Sunday August 07, 2011 @03:52AM (#2856131)
Also worth mentioning pythonbrew which goes a step further and allows you to manage separate Python builds.
Re:Beginners Guide : pip and virtualenv by waterside81 on Sunday August 07, 2011 @11:55AM (#2856864)
pip & virtualenv saved me a world of hurt upgrading from Snow Leopard to Lion. The upgrade completely wiped out any global packages I had in Python/2.6 - so I did lose a few packages that I needed to rebuild, but not many.