[issue20883] Windows 'for current user' installation - 32/64-bit registrations overwrite each other

[Steve Dower]

Steve Dower added the comment:

I would be in favour of having separate keys for 32-bit and 64-bit installs (in addition to the current one, if dropping it completely is not an option). We use the registry keys in PTVS (http://pytools.codeplex.com/) to detect installed interpreters, so the collision here means we can only detect one per-user interpreter per-version.

We haven't received many complaints about this, so we assume that not many people install both the 32-bit and 64-bit versions of Python. However, we do it all the time, so we'd be happy with a fix just for us :)

As far as the redirection goes, that is largely a compatibility 'feature' for running 32-bit programs on 64-bit Windows. HKEY_CURRENT_USER\Software\Wow6432Node is not official (even though there's some buggy software that thinks it is...) and doesn't mean anything (while the one in HKEY_LOCAL_MACHINE does).

The intent is that software uses differently named keys when storing different settings. Having "Python\PythonCore\3.4", "3.4-32" and/or "3.4-64" seems appropriate to me (where the "3.4" value keeps the current last-one-wins behaviour).

Out of interest, what other issues exist for the per-user installation? I normally prefer it because I like keeping the DLLs out of System32, and I practically never hit any issues (Python 2.5 has one with virtualenv, but that's about it).

----------
nosy: +steve.dower

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20883>
_______________________________________