On Wed, Nov 21, 2012 at 5:23 PM, Issam Outassourt <[email protected]> wrote: > Well, I do not totally agree with your point. > The problem with virtual environments such as these is that you have trouble > sometimes figuring out what actually happens behind the scripts that are > used to initialize your environment. Thus comes a natural habit that I > personally developed which is to say, whatever external tool that you need a > specific version for, get the latter version and install it within a > directory that would look like something of this kind /external/django/bin/ > And add that directory to your Django project path in your settings.py > This has the advantage to let you know when you deploy your app, which are > the real specifics that you need to install back again on your development > server. > > Did that help ? > Again, it's my personal opinion. Be careful to choose what suits you.
virtualenv doesn't actually do any 'magic behind the scenes', it simply changes your $PATH so that the correct python interpreter is found, and hence uses the correct 'site-packages' folder inside your virtualenv. I personally think manually manipulating sys.path inside your settings, or inside your wsgi file, is much more troublesome. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
