[issue25405] User install of 3.5 removes py.exe from C:\Windows

Steve Dower added the comment: I believe this issue is fixed (as of 3.5.1), and I don't specifically know what I'd do to make it more fixed, so I'm closing this. Changing the configuration of the launcher is a separate discussion. -- resolution: -> out of date stage: -> resolved stat

[issue25405] User install of 3.5 removes py.exe from C:\Windows

Changes by Vinay Sajip : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue25405] User install of 3.5 removes py.exe from C:\Windows

eryksun added the comment: Setting a new default for py.exe doesn't require admin privileges. You can use the PY_PYTHON environment variable: C:\>py --version Python 2.7.10 C:\>set PY_PYTHON=3 C:\>py --version Python 3.5.0 which you can easily persist in the registry usin

[issue25405] User install of 3.5 removes py.exe from C:\Windows

Terry J. Reedy added the comment: In my view, py.exe is a mess. Steve, I know this is something you just inherited. I have multiple all-user installs. The first problem I have with py.exe is its defaulting to 2.7 instead of latest 3.5, and the impossibility of changing this. The second, gi

[issue25405] User install of 3.5 removes py.exe from C:\Windows

Steve Dower added the comment: Part of this will be the upgrade from RC, which will behave differently from the next upgrade to 3.5.1. But I have just made some fixes in how upgrading the launcher is handled, so there's a chance this is already fixed. But I'll test this scenario too. Do you r

[issue25405] User install of 3.5 removes py.exe from C:\Windows

New submission from Paul Moore: I have had a user install of Python 3.5rc3 for some time on one of my PCs. It also had plenty of other versions on there - 3.4, 3.3, 2.7 and 2.6. The 3.5rc3 install was a user install. I have my Python 3.4 install set up on PATH, and I've configured py.ini to ru