This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: 3.5.0a2 Windows installer does not remove 3.5.0a1
Type: Stage: resolved
Components: Windows Versions: Python 3.5
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: steve.dower Nosy List: BreamoreBoy, python-dev, steve.dower, tim.golden, zach.ware
Priority: normal Keywords:

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) * (Python committer) 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) * (Python committer) 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 for 3.5.0a*.

I think switching to $(Major).$(Minor).$(Field3Value).0 is correct here - this should give us,, for 3.5.0a1-3, then 3.5.1100.0 for 3.5.1a1, etc.
msg237578 - (view) Author: Roundup Robot (python-dev) (Python triager) 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.
msg237580 - (view) Author: Steve Dower (steve.dower) * (Python committer) 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) * (Python committer) Date: 2015-04-14 21:28
Steve confirmed in person at PyCon that this is fixed.
msg241066 - (view) Author: Steve Dower (steve.dower) * (Python committer) 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...
Date User Action Args
2022-04-11 14:58:13adminsetgithub: 67800
2015-04-15 01:05:04steve.dowersetmessages: + msg241066
2015-04-14 21:28:30zach.waresetstatus: open -> closed
resolution: fixed
messages: + msg241032

stage: resolved
2015-03-08 22:36:18steve.dowersetmessages: + msg237580
2015-03-08 22:29:51python-devsetnosy: + python-dev
messages: + msg237578
2015-03-08 20:16:59steve.dowersetmessages: + msg237566
2015-03-08 19:39:43BreamoreBoysetnosy: + BreamoreBoy
2015-03-08 19:33:14steve.dowercreate