Bug report

For some of my projects, I build my own Windows installers from source using theTools\msi\buildrelease.bat script. For Python 3.9.7 and higher, the installers I build locally are no longer interoperable with those that are released officially. For example, if I have an official Python 3.9.13 installation, I can't upgrade it using a locally-built Python 3.9.14 installer. My locally-built installer does not recognize that there already exists a 3.9.x installation that can be upgraded, and it asks me to do a completely new installation.

I traced the cause of this to#27458, which first appeared in Python 3.9.7. In particular, in the fileTools\msi\buildrelease.bat, the line

setRELEASE_URI=http://www.python.org/{arch}

was changed to

setRELEASE_URI=https://www.python.org/{arch}

However, based on my understanding, official releases still use the valuehttp://www.python.org/{arch}, as evidenced by the line

ReleaseUri: http://www.python.org/{arch}

inhttps://github.com/python/release-tools/blob/master/windows-release/stage-msi.yml
TheRELEASE_URI affects the GUIDs of the installers so that installers built with differentRELEASE_URI values cannot be used to upgrade each other.

For the sake of consistency, I propose that we changeRELEASE_URI inTools\msi\buildrelease.bat back to its original value ofhttp://www.python.org/{arch}. I tried making this change locally, and that fixed my interoperability issue. I can make a pull request as well.

Your environment

• CPython versions tested on: 3.9.7 and higher
• Operating system and architecture: Windows 64-bit

(originally posted onhttps://discuss.python.org/t/divergence-between-official-releases-and-those-built-with-tools-msi-buildrelease-bat/18927)