[issue22139] python windows 2.7.8 64-bit did not install

STINNER Victor added the comment: No activity since 2016, I close the issue. -- nosy: +vstinner resolution: works for me -> out of date status: open -> closed ___ Python tracker _

[issue22139] python windows 2.7.8 64-bit did not install

Henning von Bargen added the comment: A belated update... What I'm trying is similar to virtualenv: My application should not depend on any pre-installed Python and not have any influence on it (and it should not modify the registry or the system environment variables). It should be noted tha

[issue22139] python windows 2.7.8 64-bit did not install

Martin v. Löwis added the comment: Reopening for somebody to look at; I'm not interested in Python 2.7 anymore. -- status: closed -> open ___ Python tracker ___ _

[issue22139] python windows 2.7.8 64-bit did not install

Henning von Bargen added the comment: Martin, while I technically understand your anwers, I have to say that from an ordinary developer's perspective, the behavior is actually *not* expected. It may be expected for python-dev experts, but not for those who are just programming _with_ python.

[issue22139] python windows 2.7.8 64-bit did not install

Martin v. Löwis added the comment: How so? Every single sentence in this section is absolutely correct. It just doesn't talk about finding builtin modules at all, only about modules found on the Python path (.py and .pyd files). Builtin modules don't have to be found, because they are, well, b

[issue22139] python windows 2.7.8 64-bit did not install

Henning von Bargen added the comment: > Installing different 2.7 versions on the same machine isn't really supported, > although it should work if they are all installed "just for me". Sigh... I've come to the same conclusion. Nevertheless it seems to me that the actual behavior is different f

[issue22139] python windows 2.7.8 64-bit did not install

Martin v. Löwis added the comment: Henning: if you have installed Python 2.7.5 "for all users", then this behavior is expected. Python finds python27.dll in system32, so even if you install 2.7.8 "just for me", it will still pick up 2.7.5 from system32. Installing different 2.7 versions on the

[issue22139] python windows 2.7.8 64-bit did not install

Henning von Bargen added the comment: The only "solution" I could find was to give up running 2.7.8 next to 2.7.5, then uninstall 2.7.8, then install 2.7.8 with the "install for all users" option selected. -- ___ Python tracker

[issue22139] python windows 2.7.8 64-bit did not install

Henning von Bargen added the comment: I don't see how this sys.path is related to the online help section "3.3.3. Finding modules". Where does c:\windows\python27.zip come from? And why does Python have to install anything in the Windows directory at all? -- __

[issue22139] python windows 2.7.8 64-bit did not install

Henning von Bargen added the comment: Sorry, of course it's NOT OK, because there's still C:\WINDOWS\system32\python27.zip as the second entry. BTW the relevant environment variables: Path=c:\python278;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\lisa\Kronos\reporting\lib\win32-x

[issue22139] python windows 2.7.8 64-bit did not install

Henning von Bargen added the comment: The online help says: """ When Python is hosted in another .exe (different directory, embedded via COM, etc), the “Python Home” will not be deduced, so the core path from the registry is used. Other “application paths” in the registry are always read. """

[issue22139] python windows 2.7.8 64-bit did not install

Henning von Bargen added the comment: Perhaps this issue should be re-opened. I stumbled across a similar issue today, and made some potentially useful observations. On a machine with an existing c:\python27 directory (Python 2.7.5), I installed Python 2.7.8 with the "install just for me" opt

[issue22139] python windows 2.7.8 64-bit did not install

Changes by Zachary Ware : -- components: +Windows stage: -> resolved type: crash -> behavior ___ Python tracker ___ ___ Python-bugs-l

[issue22139] python windows 2.7.8 64-bit did not install

Martin v. Löwis added the comment: Since we can't investigate further (since you have now resolved it for you), closing it as suggested. -- resolution: -> works for me status: open -> closed ___ Python tracker __

[issue22139] python windows 2.7.8 64-bit did not install

Andreas Richter added the comment: I think we can close this although there should be some kind of warning that running an upgrade without an uninstall may not upgrade the files in some cases. However I can't really tell what those cases are. Since I deleted all the files and then did a repair

[issue22139] python windows 2.7.8 64-bit did not install

Andreas Richter added the comment: Ok, complete uninstallation of 2.7.8 and then reinstalling did give me the new executable. In my use case I do not register extensions or add python to the path so I did not expect anything to be left over as "registration" of 2.7.5 previously, but I guess it

[issue22139] python windows 2.7.8 64-bit did not install

Andreas Richter added the comment: Well I know I tried the installation and uninstallation multiple times. I also deleted the binaries and did a repair. Each time the old binaries came back. So I suppose there could be an old registered msi database be getting in the way. But since the non-bin

[issue22139] python windows 2.7.8 64-bit did not install

Terry J. Reedy added the comment: I downloaded the 2.7.8 64-bit msi, installed over 2.7.7, and indeed got 2.7.8, which inports hmac fine. Andreas, did you have 2.7.5/6 installed before? If so, I strongly suspect that the installer did not run (correctly). There might be an error log somewhere