I generally run it exactly as "python scripts/pinax-boot.py ../pinax-env", and I don't get anything put into ~/pinax-env, I'm not sure why you are.
Are you saying when you give an absolute path to the pinax-env it all works out? If so I'll update the docs to mention that.
On Sun, Jan 23, 2011 at 8:00 PM, Yarko <yar...@gmail.com> wrote:I'm probably just missing something simple -
macbook-pro; python 2.6.5; virtualenvironmentwrapper;
IF I read this right, when I I go into Pinax-0.7.3-bundle, and run:
$ python scripts/pinax-boot.py ../pinax-env
I get some things put in ../pinax-env, and some in ~/pinax-env...
Giving an absolute path to pinax-boot.py seems to solve this much.
...just for completeness: giving an absolute path (other than WORKON_HOME) works but if you use virtualenvwrapper, the activation would be inconsistent with all your other virtual activations, so I wouldn't recommend putting that in the documentation.