So it seems counter intuitive but you might also have luck just reinstalling Python3.8 back over top. If the uninstall was botch then that should put everything back in place and then you can just run the uninstall again and see if it clears out this time. Otherwise I agree with stack overflow you can just go in and do it manually. If you have multiple Python installs I would recommend make sure to use the py launcher instead of adding any of the Pythons to the Windows path. I also don't like the new default install location in the program folders for development machines and find that it can sometimes cause conflicts so for those machines where I need multiple versions I still install Python on the root of the the C drive or and additional hard drive and name the folders PythonXX_32 or 64 depending on the type of install where XX is of course the major and minor version 36, 37, 38 etc. Then I use py -3.6 and so on to execute the different installs from the command line.
On Tue, May 4, 2021 at 2:10 AM Sian Doherty <sdohert...@gmail.com> wrote: > Thanks for the advice. I found a stack overflow post that suggested just > removing manually and cleaning out the registry too. I think I have it > under control but I haven't gotten around to reinstalling it yet. > > On Sun, 2 May 2021, 10:05 Mats Wichmann, <m...@wichmann.us> wrote: > > > On 4/29/21 6:59 PM, Sian Doherty wrote: > > > I’m trying to uninstall Python 3.8.5 on Windows 10 Pro 20H2 as I had > > multiple environments and as a result corrupted them. > > > > > > When I uninstall from control panel, it takes less than a second and > > says it uninstalled successfully but I can still access python through > the > > command prompt by typing python. > > > > > > Is there a different way to uninstall that isn’t through the control > > panel? I would have thought I would do that and then clean out the > registry > > separately and the %localappdata%\pip folder. > > > > > > Any thoughts? > > > > There are some uninstall tools, of varying quality. Some depend on you > > having been running them while the install happened, which is probably > > not the case for you. Once you've messed up Windows' idea of the install > > subsystem, it's not that easy to recover. Though some may disagree, > > that's not really Python's fault, the install system seems pretty > > fragile. Sometimes if the the files needed to process the uninstall > > have been removed but the uninstall itself didn't finish you're in > > trouble - which isn't really the fault of the install system, but then > > you ask how that scenario arose? anyway... > > > > You could look for this tool: > > MicrosoftProgram_Install_and_Uninstall.meta.diagcab - an Internet search > > should find it. it usually does a fairly good job of cleaning up messes > > (well - it's worked well for me in a few dire situations). > > > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list
