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

2016-01-16 Thread Steve Dower
Changes by Steve Dower : -- assignee: -> mhammond resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

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

2016-01-10 Thread Vinay Sajip
Vinay Sajip added the comment: Hey, Steve, don't shut me out, I'm still here ;-) I've had a heavy consulting load for the past year or so which means I can't always deal with issues as quickly as before. If someone else fixes issues before I get to them, it's fine by me :-) IMO the proposed

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

2016-01-10 Thread Steve Dower
Steve Dower added the comment: > I've had a heavy consulting load for the past year or so which means I can't > always deal with issues as quickly as before. That explains it :) With so little visibility into what we're doing outside of Python it's hard to know. Glad you're still about.

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

2016-01-09 Thread 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

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

2016-01-09 Thread Steve Dower
Steve Dower added the comment: I don't think Vinay does much wrt the launcher in core anymore, it's mostly been me recently. I don't see any harm in this change, though I'll admit I also don't see the point. When is the launcher ever going to find Python built in-place? --

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

2016-01-09 Thread Mark Hammond
Mark Hammond added the comment: > When is the launcher ever going to find Python built in-place? On the machine that built Python in-place :) I have a dev environment where all Python versions and pywin32 are built and that's the environment where py.exe is failing. My build scripts use