pinax-boot.sh calls pinax-env/bin/pip without verifying that it exists. If
you're on a system which
already has pip installed, that file won't exist because the installer returns
successfully if pip exists
anywhere in the system path.
I used pinax-boot.sh --no-site-packages to work around this but this situation
should be handled
more gracefully - adding --always-copy to the easy_install line in
pinax-boot.sh solves that
problem but probably needs a >=0.3 to avoid breaking on git / hg URLs.
What version of the product are you using? On what operating system?
Mac OS X 10.5 using the system Python 2.5
Original issue reported on code.google.com by adamsc@gmail.com on 21 Mar 2009 at 10:34
Original issue reported on code.google.com by
adamsc@gmail.com
on 21 Mar 2009 at 10:34