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 32-bit and 64-bit per-user Pythons with the same key name. (Previously
it would "work", but you couldn't find both of them through the registry. Now,
because of other changes, it will have more serious issues.)
Changing to "3.5-64" and "3.5-32" and not use "3.5" anymore was inconsistent
with the launcher, but that's a fairly weak reason. There just didn't seem to
be a stronger reason to change.
(I don't consider this a bug, so I'm closing, but if Barry or someone else
wants to argue that it should be changed then I'm willing to consider it for
3.6. I don't think changing it for 3.5.1 is a good move at this point.)
----------
components: +Windows
nosy: +paul.moore, tim.golden, zach.ware
resolution: -> not a bug
status: open -> closed
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25148>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
