Can't run Python Launcher on Windows

[BreamoreBoy]

BPO	25089
Nosy	@terryjreedy, @pfmoore, @tjguk, @zware, @zooba
Files	Python 3.5.0 (64-bit)_20150913191600.log: Main log file as requested. Python 3.5.0 (64-bit)_20151207124434_000_launcher_AllUsers.log: The only launcher log in the directory.

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/zooba'
closed_at = <Date 2016-01-16.20:01:31.065>
created_at = <Date 2015-09-13.22:44:57.329>
labels = ['type-bug', 'OS-windows']
title = "Can't run Python Launcher on Windows"
updated_at = <Date 2016-01-16.20:01:31.064>
user = 'https://bugs.python.org/BreamoreBoy'

bugs.python.org fields:

activity = <Date 2016-01-16.20:01:31.064>
actor = 'steve.dower'
assignee = 'steve.dower'
closed = True
closed_date = <Date 2016-01-16.20:01:31.065>
closer = 'steve.dower'
components = ['Windows']
creation = <Date 2015-09-13.22:44:57.329>
creator = 'BreamoreBoy'
dependencies = []
files = ['40461', '41263']
hgrepos = []
issue_num = 25089
keywords = []
message_count = 19.0
messages = ['250588', '250591', '250592', '250594', '250604', '250611', '250664', '250670', '252555', '252556', '256064', '256069', '256080', '256086', '256088', '256095', '256100', '258403', '258404']
nosy_count = 7.0
nosy_names = ['terry.reedy', 'paul.moore', 'tim.golden', 'BreamoreBoy', 'python-dev', 'zach.ware', 'steve.dower']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25089'
versions = ['Python 3.5']

[BreamoreBoy]

I first asked a few days ago, see this thread http://www.gossamer-threads.com/lists/python/python/1216917. You can work around it by running "repair" but it takes an age to run for what, to me anyway, is a minor irritant.

[zooba]

I don't understand what you did and what the result was from that thread.

• What options did you select when installing 3.5?
• What other Python versions did you have? What options were used to install them?
• Where was py.exe before installing 3.5?
• Can you attach all of the logs from your 3.5 install (from your %TEMP%)?

[terryjreedy]

For anyone else reading this, Mark says he already re-tried with 3.5.0.

The only problem I had with the install on my Win7, with 2.7.10, 3.4.3, and 3.5.0rc3 already present, is that 3.4.3 is still the default python (started by 'python') in spite of checking everything relevant when installing 3.5.0.

[zooba]

Yeah, it's basically impossible to manage PATH automatically. You've probably installed 3.5 just for yourself while 3.4 is installed for all users. In this case, 3.5 will always lose because Windows puts user paths after system paths.

You could modify 3.4 to remove it from PATH or use py.exe, which resolves versions correctly. Or you can modify your PATH manually.

[terryjreedy]

I did installed 3.5 for all users. Logging into another user and back changed 'python' association. So ok now.

[BreamoreBoy]

I install for all users, don't put Python on the PATH, other than that I think everything is selected.

I've 2.6, 2.7. 3.3 and 3.4. I had 3.5.0rc4 and upgraded the existing installation to 3.5.0 full release.

I've no idea where py.exe was, but it is now in C:\Windows. This is what I expect having just read PEP-397.

Do you really want all logs from the 3.5.0 install and the repair, that's 21 files? It's an odd number as there is no log file for the launcher in the install but there is in the repair. The same is true for the rc4 logs.

[zooba]

Just the main log file from the initial install is enough if there's no log for the launcher. It probably means the initial setup startup deselected it for some reason.

[zooba]

Yep, as part of the upgrade detection we're choosing not to install the launcher. Not sure whether that's because of a bug or a previous install on your machine, but I'll take a closer look.

[python-dev]

New changeset 1e99ba6b7c98 by Steve Dower in branch '3.5':
Issue bpo-25089: Adds logging to installer for case where launcher is not selected on upgrade.
https://hg.python.org/cpython/rev/1e99ba6b7c98

[zooba]

Hopefully with the extra logging we'll be able to see if something is failing at the point of detection. Any failure here (permissions in registry, etc.) will cause the launcher to not be installed on upgrade (which might be the same as removing it... I need to spend more time working through the dependencies involved here because they are messy).

[BreamoreBoy]

After running the 3.5.1 64 bit web installer the py launcher has again been lost, i.e. "'py' is not recognized as an internal or external command, operable program or batch file." Running the web installer in "repair" mode hasn't made any difference. I've attached the log file for the removal of the 3.5.0 launcher, but there are no launcher files with the 3.5.1 install or repair.

[zooba]

There's a separate issue in the 3.5.1 installer where the launcher is always deselected on upgrade. I'm currently working on a fix to force it to always install and we might push out a new 3.5.1 build later today.

If you go through Modify rather than Repair then you can select to install the launcher.