Steve Dower <steve.do...@python.org> added the comment:
It looks like the best solution here may be to rename the bundled executables
to "python3.8.exe" etc. rather than "python.exe".
We will still keep the "python.exe" alias, and sys.executable won't change
(it'll still point to the stable alias), but by having the "core" executable be
named differently between Python versions it'll fix a couple of minor issues.
Most importantly here, because the registry path would then point at
"python3.8.exe" rather than "python.exe", it becomes more likely that the
global alias will remain enabled and so launching via the registry path will
work. The downside is that apps that use "$InstallPath\python.exe" rather than
"$ExecutablePath" will not work. But the ExecutablePath value has been present
for a while now, and PEP 514 specifies it as preferred when available, so I
think that's okay.
We can also include a plain "python[w].exe" in the installation, but that'll
only be useful for subprocess.run("python") from the same version - it won't be
executable at all from outside the app package.
(None of this affects the regular installer, FWIW. That'll still be plain
"python.exe".)
Anyone have any thoughts or concerns?
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue37734>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
