Comment 3 for bug 1266550

I've found a few bugs that seem related:

https://github.com/pypa/pip/issues/1133
https://github.com/pypa/pip/issues/317

Both of these were reported solved in https://github.com/pypa/pip/pull/1146 which seems to have landed in pip 1.5 - which would explain why I can reproduce this in versions <1.5

Using the version of virtualenv from the ubuntu sources for precise (python-virtualenv (1.7.1.2-1)) I was able to create a virtualenv with pip 1.1, and can replicate the problem inside a virtualenv. I then upgraded with "pip install pip==1.4.1" and can still replicate the problem. I then upgraded with "pip install pip==1.5", then used "pip install --no-use-wheel diskimage-builder" to get around the old version of setuptools in the virtualenv - and confirmed that the scripts now get +x set.

So in short, I'm fairly convinced that this is caused by using pip <1.5