[issue30405] build.bat: register binaries for py launcher

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue30405] build.bat: register binaries for py launcher

Change by Eryk Sun : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.7 ___ Python tracker ___ ___ Python-bugs-list maili

[issue30405] build.bat: register binaries for py launcher

Change by Eryk Sun : -- Removed message: https://bugs.python.org/msg293989 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue30405] build.bat: register binaries for py launcher

Steve Dower added the comment: > Steve, I gather you don't think it's a problem to use arbitrarily named tags > on the command line. The launcher shouldn't look for an "h" tag for `py -h` Sure, we can reserve some tags - the -x/y syntax would let you refer to a conflicting one. But other than

[issue30405] build.bat: register binaries for py launcher

Eryk Sun added the comment: The existing code can be adapted to generalize support for version-number tags, i.e. X.Y[-32|-64]. locate_all_pythons() would need to search every company key to add executable installations that use version-number tags to the installed_pythons array. Whether a tag

[issue30405] build.bat: register binaries for py launcher

Steve Dower added the comment: My thinking was basically to use an algorithm like this: if sys.argv[1].startswith('-'): company, _, tag = sys.argv[1][1:].rpartition('\') if company: # look for Tag under Company else: # look for tag under Python

[issue30405] build.bat: register binaries for py launcher

Eryk Sun added the comment: Supporting PEP 514 tags is an interesting idea, but maybe you could go into more detail about what you have in mind. Are you thinking of using the SysVersion, SysArchitecture, and [Windowed]ExecutablePath fields where available instead of parsing version tags and as

[issue30405] build.bat: register binaries for py launcher

Steve Dower added the comment: I am most interested in making py.exe follow PEP 514 and look up tags. Given this, we could register builds as "PythonCore\Dev" and then use "py.exe -dev" to run the most recent build. At worst, we only have one lingering registration (and a positive - it would b

[issue30405] build.bat: register binaries for py launcher

Terry J. Reedy added the comment: >From a couple of tests, the local python.bat should be satisfactory for most >of my current uses. Being part of a #30362 listing would be nice, but I don't >often change my set of build binaries. -- ___ Python tra

[issue30405] build.bat: register binaries for py launcher

Eryk Sun added the comment: The launcher could be extended to support additional suffixes in the version string. Currently -32 is supported after the minor version number (e.g. 3.6-32), and (per a recent update) the latest version of the launcher will also support -64, with and without specify