Paul Hammant added the comment: Chronalog for today, below. Status - can reproduce at will, can't produce %TEMP% files was for - there aren't any.
0. I deleted all Python prefixed files from %TEMP% 1. I uninstalled Python 3.4 via it's windows installer. It progressed to completion. I noted after that there was still a C:\python34 directory with some remaining items in it. There was also still a PYTHONHOME environmental variable. 2. I installed Python 2.7 via it's canonical windows installer, and (as per this bug filing) it barfs, and then (with a couple of clicks from me) proceeds to undo the installation. 3. I've checked the %TEMP% folder. There's nothing in there with a matching timestamp, nor anything at all prefixed with 'Python' 4. If I redo #2 and explicitly de-select pip, the installation completes as expected. 5. If I uninstall (via the installer) and attempt to reinstall WITH pip, it barfs (as per this bug filing) 6. If I delete the PYTHONHOME env-var and attempt, it works. Conclusion - Pip aspect of WindowsInstaller gets caught out on presence of erroneous PYTHONHOME. It does so for Python 2.7.x replaceing and Python 3.5.x or the opposite order. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26119> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
