[issue25148] Windows registry PythonCore key changed inconsistent with other releases

Mark Hammond added the comment: It appears bdist_wininst wasn't updated for this so installed created by distutils don't work in 32bit versions - is there a different bug open for that? (Or I'm doing something wrong, but the installer fails and a quick scan of the source doesn't seem to

[issue25148] Windows registry PythonCore key changed inconsistent with other releases

Steve Dower added the comment: That's a possibility. I won't have a chance to check for a few days, but it should get another bug if it's wrong. -- ___ Python tracker

[issue25148] Windows registry PythonCore key changed inconsistent with other releases

Steve Dower added the comment: The per-user installs collide without the name change, and since those are now the default, it's important to have the change. The redirection you refer to only occurs for HKLM and not HKCU. The launcher was updated and tested to find all versions. If there's a

[issue25148] Windows registry PythonCore key changed inconsistent with other releases

Mark Hammond added the comment: > and the launcher was actually updated to match the registry key > directly, rather than special-casing the "-32" suffix It appears this has broken the launcher. A freshly-built py.exe from Python 3.5 doesn't seem to find older 32bit versions, while py.exe from

[issue25148] Windows registry PythonCore key changed inconsistent with other releases

Mark Hammond added the comment: > The original naming ("3.5") can't be used because you can't > simultaneously install 32-bit and 64-bit per-user Pythons with the same > key name. They will be in different nodes - the 32bit version would be under Wow6432Node. The py.exe launcher had no issues

[issue25148] Windows registry PythonCore key changed inconsistent with other releases

Barry Scott added the comment: To clarify: 3.5 means 3.5 64 bit 3.5-32 means 3.5 32 bit You do not add the -64 as it is the default. However: this change should have been in the "What's New" as it breaks Windows installation code for extensions. --

[issue25148] Windows registry PythonCore key changed inconsistent with other releases

Steve Dower added the comment: It was changed to be consistent with the PEP 397 launcher (and the launcher was actually updated to match the registry key directly, rather than special-casing the "-32" suffix). The original naming ("3.5") can't be used because you can't simultaneously install

[issue25148] Windows registry PythonCore key changed inconsistent with other releases

Changes by Ezio Melotti : -- nosy: +steve.dower type: -> behavior ___ Python tracker ___

[issue25148] Windows registry PythonCore key changed inconsistent with other releases

New submission from Barry Scott: I am used to looking in HKLM:\SOFTWARE\Python\PythonCore\%(py_maj)d.%(py_min)d\InstallPath to find out where python is installed so that my installation kit can add itself to site-packages. I just found that the registry key used for 32 bit python 3.5 on