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.

classification
Title: Uninstalling Python 3.5 removes a "py.exe" that was installed with Python 3.4
Type: Stage:
Components: Installation, Windows Versions: Python 3.5
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: steve.dower Nosy List: paul.moore, steve.dower, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2015-03-09 12:20 by paul.moore, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg237640 - (view) Author: Paul Moore (paul.moore) * (Python committer) Date: 2015-03-09 12:20
When I installed Python 3.4, I included the py.exe launcher. I have just installed Python 3.5a0, then uninstalled it again, and the py.exe launcher has gone.

Either the 3.5 installer should notice that py.exe is already present and remember *not* to uninstall it, or it should warn the user when installing that continuing will take ownership of the launcher from a previous installation.

(I understand why having the same file owned by 2 installers causes problems, and that there's no easy fix, but the current behaviour is not at all friendly - I now have to reinstall Python 3.4 to fix it, or at least re-download the installer and try a repair, which might work I guess).
msg238123 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2015-03-15 04:34
This is already fixed for 3.5 and later, since the launcher now has a consistent component ID regardless of which version/architecture of Python is installed.

It's too late to go back and make equivalent changes to the installer for 3.4 - running a Repair on a 3.4 installation is the best way to get it back.
History
Date User Action Args
2022-04-11 14:58:13adminsetgithub: 67809
2015-03-15 04:34:43steve.dowersetstatus: open -> closed
resolution: wont fix
messages: + msg238123
2015-03-09 12:20:12paul.moorecreate