classification
Title: Python windows installer has a confusing name - add setup to its name
Type: enhancement Stage: needs patch
Components: Installation, Windows Versions: Python 3.10
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: barry-scott, mrabarnett, pablogsal, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2021-02-07 18:15 by barry-scott, last changed 2021-02-09 18:20 by steve.dower.

Messages (6)
msg386598 - (view) Author: Barry Alan Scott (barry-scott) * Date: 2021-02-07 18:15
New users of Python on Windows frequently confuse the Python installation program with Python itself.

They also can end up with the wrong 32 or 64 bit version.

I suggest that the installation program name is changed to include "setup" in its name. This seems to be the usually convention many Windows installation programs use.

Further users may know they are need windows 64 bit or windows 32 bit compatible software. The python installer naming is not obvious.

The windows 32 installer has no additional text to show it is targeted at windows 32.

The windows 64 uses amd64 - does not mean not for Intel CPU's for example?

Examples with both suggestions:

python-3.10.0a5.exe becomes python-setup-win32-3.10.0a5.exe
python-3.10.0a5-amd64.exe becomes python-setup-win64-3.10.0a5.exe

Barry
msg386599 - (view) Author: Matthew Barnett (mrabarnett) * (Python triager) Date: 2021-02-07 18:28
Sorry to bikeshed, but I think it would be clearer to keep the version next to the "python" and the "setup" at the end:

python-3.10.0a5-win32-setup.exe
python-3.10.0a5-win64-setup.exe
msg386600 - (view) Author: Barry Alan Scott (barry-scott) * Date: 2021-02-07 18:31
I happy with your names. I think they are better then my version.
msg386669 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2021-02-08 22:39
I agree with the idea and Matthew's version. This continuing problem is worth doing experiments.  I marked this as 'enhancement' and 3.10 only because this might break code that hardcodes the complete name.  This might also, unfortunately, be a reason to reject, but we have changed the installer name before.  Or the Windows people might decide that backports are OK.
msg386730 - (view) Author: Barry Alan Scott (barry-scott) * Date: 2021-02-09 17:56
Understood that changing the status quo may have problems.

Maybe you do an HTTP redirect from the old name to the new name?
Or have the installed available under both names but only advertise the new name?
msg386737 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2021-02-09 18:20
In principle I agree, but need to spend some time thinking about the compatibility implications. We've already changed the download page for 3.10, so changing the download names as well won't hurt too much - I don't think there's a real need for redirects.

If someone wants to prepare a patch, feel free. It'll probably impact publishing, so adding the RM for awareness.
History
Date User Action Args
2021-02-09 18:20:17steve.dowersetnosy: + pablogsal
messages: + msg386737
2021-02-09 17:56:55barry-scottsetmessages: + msg386730
2021-02-08 22:39:31terry.reedysettype: enhancement

messages: + msg386669
nosy: + terry.reedy
2021-02-08 22:32:40terry.reedysetnosy: + steve.dower, paul.moore, tim.golden, zach.ware
stage: needs patch

components: + Installation, Windows
versions: + Python 3.10
2021-02-07 18:31:48barry-scottsetmessages: + msg386600
2021-02-07 18:28:42mrabarnettsetnosy: + mrabarnett
messages: + msg386599
2021-02-07 18:15:28barry-scottcreate