Irit Katriel added the comment:
> This does not affect Python 3.5 or later.
Closing as out of date as 3.4 is no longer maintained.
--
nosy: +iritkatriel
resolution: -> out of date
stage: needs patch -> resolved
status: open -> closed
___
Python
Ethan Henderson added the comment:
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.
Steve Dower added the comment:
Thanks. Unfortunately I can't get anything helpful from that log because it's
failing too early. It seems like you have some corruption in your Windows
installer database, since it isn't even getting far enough into the Python
installer. I'd track down a
Ethan Henderson added the comment:
I have the same issue on 3.4.3 x64 on Windows 10 x64.
I set PYTHONHOME and PYTHONPATH (Just to C:/Python34), but that didn't fix the
problem.
--
nosy: +Zbee
___
Python tracker rep...@bugs.python.org
Steve Dower added the comment:
+Martin, who apparently never made it onto nosy.
You should clear those variables, run a Repair, and then uninstall. This error
typically is because pip has become corrupted and cannot be removed.
This does not affect Python 3.5 or later.
--
nosy:
Ethan Henderson added the comment:
I deleted those variables and tried running a repair but still got the
specified account already exists schpeel.
I then tried running an uninstall and got the same error as last time there too.
There's presently no pip at all; there is no python folder on
Steve Dower added the comment:
I need to see the detailed log to be any more helpful. Can you try running this
command and post the log here:
msiexec /l*vx log.txt /x {9529565F-E693-3F11-B3BF-8CD545F5F9A0}
(Note that the UUID is different from earlier because it matches 3.4.3.amd64
and the
Ethan Henderson added the comment:
Running that in my command prompt outputs Access is denied, even after
disabling UAC.
Running that in bash just gives me a popup for Windows Installer.
Is the UUID going to be different for 3.4.3 intel x64 (I have intel, not amd)?
--
Steve Dower added the comment:
Start from an elevated command prompt. There's only one 64-bit build, so
that'll be it. Our name for it is amd64, even though it applies to both Intel
and AMD.
--
___
Python tracker rep...@bugs.python.org
Ethan Henderson added the comment:
My log.txt: http://puu.sh/jqLWR.txt
Turns out that my antivirus was blocking that command from running before.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22329
J. Walter Clark added the comment:
I had the same issue using Python 3.4.2 x64 on Windows 7 x64 and resolved it by
setting PYTHONHOME and PYTHONPATH environmental variables.
--
nosy: +jwalterclark
___
Python tracker rep...@bugs.python.org
New submission from Llelan D.:
Python v3.4.1 x64 on Windows 7 x64.
If the python installation directory is deleted, the installer can not remove,
change, or repair the installation.
When I run the python-3.4.1.amd64.msi installer and choose Remove, it gives me
a dialog saying a required file
Terry J. Reedy added the comment:
I and at least one other person reporting on python-list have had similar
problems trying to update an installation.
--
nosy: +terry.reedy
stage: - needs patch
versions: +Python 3.5
___
Python tracker
Steve Dower added the comment:
I've been working on the rewrite for 3.5 already (progress at
http://hg.python.org/sandbox/steve.dower) - redoing the installer completely
was one of the conditions for when I signed on to own it.
Martin is still responsible for 3.4, and I'm building 2.7 as
14 matches
Mail list logo
