Beginners Guide : pip and virtualenv
mahdiyusuf.com
Beginners Guide : pip and virtualenv
1–10 of 15 posts
Re: Beginners Guide : pip and virtualenv
#2You should try virtualenvwrapper, it makes the process of activating and changing between virtualenvs a breeze.
Re: Beginners Guide : pip and virtualenv
#3You should try virtualenvwrapper, it makes the process of activating and changing between virtualenvs a breeze.
upcoming post :P
Re: Beginners Guide : pip and virtualenv
#4You should try virtualenvwrapper, it makes the process of activating and changing between virtualenvs a breeze.
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
#5Also worth mentioning pythonbrew which goes a step further and allows you to manage separate Python builds.
Re: Beginners Guide : pip and virtualenv
#6You should try virtualenvwrapper, it makes the process of activating and changing between virtualenvs a breeze.
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.
Re: Beginners Guide : pip and virtualenv
#7One 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
#8One 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.
Except for when you DO want to install a package globally. Utilities like pyflakes and fabric, for example.
Re: Beginners Guide : pip and virtualenv
#9One 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.
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.
Re: Beginners Guide : pip and virtualenv
#10Nice 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.