Issue 23612: 3.5.0a2 Windows installer does not remove 3.5.0a1 (original) (raw)

Created on 2015-03-08 19:33 by steve.dower, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (6)
msg237556 - (view)	Author: Steve Dower (steve.dower) *	Date: 2015-03-08 19:33
Currently, 3.5.0a1 needs to be manually removed either before or after installing 3.5.0a2 (after *should* be okay, but before is preferable). Installing a later version should detect and remove the earlier one. This is obviously an installer bug.
msg237566 - (view)	Author: Steve Dower (steve.dower) *	Date: 2015-03-08 20:16
Looks like the way I was calculating the version number of the installer didn't take into account a2 and a3 - we had 3.5.0.10 for 3.5.0a*. I think switching to (Major).(Major).(Major).(Minor).$(Field3Value).0 is correct here - this should give us 3.5.100.0, 3.5.101.0, 3.5.102.0 for 3.5.0a1-3, then 3.5.1100.0 for 3.5.1a1, etc.
msg237578 - (view)	Author: Roundup Robot (python-dev)	Date: 2015-03-08 22:29
New changeset 97e01e107591 by Steve Dower in branch 'default': Issue #23612: Fixes upgrade code and version for Windows installer. https://hg.python.org/cpython/rev/97e01e107591
msg237580 - (view)	Author: Steve Dower (steve.dower) *	Date: 2015-03-08 22:36
Two parts to this - first that I was using the wrong version, but also the wrong upgrade code for the bundle. Those are both fixed now, but it does mean that both 3.5.0a1 and a2 will need to be manually uninstalled. It is possible to add a list of the upgrade codes that have already been released and remove those too, but since they are only alphas I'm not worried about requiring manual uninstall of those versions.
msg241032 - (view)	Author: Zachary Ware (zach.ware) *	Date: 2015-04-14 21:28
Steve confirmed in person at PyCon that this is fixed.
msg241066 - (view)	Author: Steve Dower (steve.dower) *	Date: 2015-04-15 01:05
To be precise, 3.5.0a3 and later will uninstall 3.5.0a2 and later. 3.5.0a1 has to be uninstalled manually, because it's the one with the bug...