Comment 11 for bug 780220

Ok, regarding my previous comment: this seems to have been caused by a particular of my setup. My python virtualenv was in ~/usr/local... and this was being 'corrected' by the setup script to ~/local...

So, moving my virtualenv seems to avoid this problem: worth knowing for anyone who likes to install things under ~/usr.

The installation is now failing with a permissions error - it is obviously attempting to install into /usr/local/lib - even though I'm within a virtualenv. I don't understand this, but it's not part of this bug so I'll leave it.

Summary: this bug is considered fixed but I think the fix breaks for users who have use ~/usr... in their virtualenv.