This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Zbee
Recipients LlelanD, Zbee, jwalterclark, loewis, steve.dower, terry.reedy
Date 2015-08-06.14:09:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1438870181.73.0.356487381913.issue22329@psf.upfronthosting.co.za>
In-reply-to
Content
I managed to resolve the issue following these steps:
1. Installing Python 3.4.3 on another computer (not even the same architecture)
2. Copying the Python34 folder from that other computer to the computer I broke
3. Running the uninstaller for Python 3.4.3
4. Reinstalling Python 3.4.3 normally as it is now removed correctly

I also replicated this error in 2.7.10 and fixed it with only slightly different steps:
1. Installing Python 2.7.10 on another computer (again, not even the same architecture as the broken computer)
2. Copying the Python27 folder from that other computer to the computer I broke
3. Running the repair tool for Python 2.7.10
4. Running the uninstaller for Python 2.7.10
5. Reinstalling Python 2.7.10 normally as it is now removed correctly

I replicated the issue in 2.7.10 again afterwards, and it does appear that step 3 is required.
History
Date User Action Args
2015-08-06 14:09:41Zbeesetrecipients: + Zbee, loewis, terry.reedy, steve.dower, LlelanD, jwalterclark
2015-08-06 14:09:41Zbeesetmessageid: <1438870181.73.0.356487381913.issue22329@psf.upfronthosting.co.za>
2015-08-06 14:09:41Zbeelinkissue22329 messages
2015-08-06 14:09:40Zbeecreate