Message270780
| Author |
busfault |
| Recipients |
busfault, paul.moore, steve.dower, tim.golden, zach.ware |
| Date |
2016年07月18日.17:18:29 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1468862309.16.0.296035283587.issue27564@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|