Tom Middleton added the comment:

Ok, so really bizarre. I uninstalled 2.7.11, then I was getting the same error 
with the 2.7.11 msi. So I was thinking that I should go back to the original 
version I had installed (2.7.10) the installer showed a "repair" option so I 
did that, then the 2.7.11 install worked.
And then the 2.7.12 installer worked.

I would have to agree with Steve Dower. I think that it had something to do 
with pip because there were a couple cmd windows that popped up during the 
install process that showed something to do with pip which didn't the first 
time I ran the installer.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27564>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to