[issue34142] Windows launcher version lookup flawed

Change by Eryk Sun : -- type: behavior -> enhancement versions: +Python 3.10 -Python 3.7 ___ Python tracker ___ ___ Python-bugs-list

[issue34142] Windows launcher version lookup flawed

Change by Steve Dower : -- versions: +Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34142] Windows launcher version lookup flawed

Eryk Sun added the comment: This line in the docs is incorrect: If PY_PYTHON=3 and PY_PYTHON3=3.1, the commands python and python3 will both use specifically 3.1 It implies that setting the `python` virtual command to "3" or "2" will use the configured version of the `python3` or `p

[issue34142] Windows launcher version lookup flawed

LarryZA added the comment: https://docs.python.org/3/using/windows.html Section 3.4.4.2 -- ___ Python tracker ___ ___ Python-bugs-

[issue34142] Windows launcher version lookup flawed

Steve Dower added the comment: The behavior is correct, so the documentation needs fixing. Which page has that example on it? Is it assuming that you only have 3.1 installed? -- assignee: -> docs@python components: +Documentation nosy: +docs@python _

[issue34142] Windows launcher version lookup flawed

New submission from LarryZA : In the manual it says that the following .ini file will cause the launcher to run Python3.1 for calls of `py` or `py -3` [defaults] python=3 python3=3.1 On my Windows 7 machine I have Python2.7-32, Python3.4-64, and Python3.7-64 (installed in that order). Setti