[issue43156] Python windows installer has a confusing name - add setup to its name

Steve Dower added the comment: 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

[issue43156] Python windows installer has a confusing name - add setup to its name

Barry Alan Scott added the comment: 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? -- __

[issue43156] Python windows installer has a confusing name - add setup to its name

Terry J. Reedy added the comment: 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 rej

[issue43156] Python windows installer has a confusing name - add setup to its name

Change by Terry J. Reedy : -- components: +Installation, Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware stage: -> needs patch versions: +Python 3.10 ___ Python tracker

[issue43156] Python windows installer has a confusing name - add setup to its name

Barry Alan Scott added the comment: I happy with your names. I think they are better then my version. -- ___ Python tracker ___ ___

[issue43156] Python windows installer has a confusing name - add setup to its name

Matthew Barnett added the comment: 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 -- nosy: +mrabarnett ___ Pyt

[issue43156] Python windows installer has a confusing name - add setup to its name

New submission from Barry Alan Scott : 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