On Wed, Jan 28, 2009 at 7:21 PM, Mike Orr <[email protected]> wrote: > On Wed, Jan 28, 2009 at 7:07 PM, Damjan <[email protected]> wrote: >> >>> In production, I've gone to always using virtualenvs. >> >> Python 2.6 now supports $PYTHONUSERBASE, just set it to a directory >> (doesn't need to exist), for example: >> >> export PYTHONUSERBASE=$HOME/mydev/ >> pip.py install FormAlchemy >> >> Now I do have in ~/.pydistutils.cfg >> [install] >> user=True >> >> It's similar to virtualenv, but kind-of more clean, and doesn't copy >> the whole python executable in each env (which I never liked). >> >> To switch to another env, just reset the variable. > > I haven't heard of this. Has anybody else compared it with Virtualenv > to see its advantages and disadvantages? What exactly does it do? > Does it do the same thing that the custom Python interpreter in the > virtualenv does, or less?
Oh, this is the same as the per-user install directory? http://www.python.org/dev/peps/pep-0370/ I thought there could be only one site-packages per user, not multiple ones per application. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
