Re: Experiences with virtualenv + Django?

Python is embedded so deeply into operating systems these days that not using virtualenv is a bad idea.  Here is what happened to me once:

1.  I went to pip intall a python package without virtualenv

2.  The installation failed leaving my python system raising an interpreter error when going to run anything python

3.  Everything on the system started breaking (yum, bash were the most noticible).

4.  I really tried to recover the box by repairing python .... installing a newer version of python .... removing and reinstalling

5.  Could not recover the linux system; it ended up being faster to rebuild it.

Don't be like me and break your system by not using virtualenv.

Brian

On Tue, May 24, 2011 at 9:42 AM, Shawn Milochik <shawn@milochik.com> wrote:

1. You can compile Python 2.6 (or 2.7) in your home directory and use that to create your virtualenvs.

2. I do 100% of my Python work with virtualenv, and would never do otherwise.

3. It is not a nightmare AT ALL, and is wonderful.

4. With pip install, pip freeze, and pip install -r it's super-easy to replicate a virtualenv.

Like you, I use Cent OS with Python 2.4 installed, but all of our apps run under Python 2.7.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
Brian Bouterse
ITng Services

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.