[New-bugs-announce] [issue26070] Launcher fails to find in-place built binaries from earlier Python versions

[Mark Hammond]

New submission from Mark Hammond:

The launcher was recently updated to look in PCBuild/win32 to support the win32 binaries being built in this directory instead of the top-level PCBuild directory. However, when this new launcher tries to find a binary for, say, Python 2.7, it doesn't find an executable because it's directly in PCBuild, not one of the win32 or amd64 sub-directories.

Note this only impacts Python when it is built in the directory - it doesn't impact installed versions.

The fix I came up with is to continue looking in PCBuild if it isn't found in one of those dirs.

Vinay, what do you think?

----------
components: Windows
files: launcher.patch
keywords: patch
messages: 257878
nosy: mhammond, paul.moore, steve.dower, tim.golden, vinay.sajip, zach.ware
priority: normal
severity: normal
status: open
title: Launcher fails to find in-place built binaries from earlier Python versions
type: behavior
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file41560/launcher.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26070>
_______________________________________