Python Launcher Matches 3.10 instead of 3.1

[Marsfan]

BPO	45616
Nosy	@pfmoore, @tjguk, @zware, @zooba, @miss-islington, @marsfan
PRs	bpo-45616: Let py.exe distinguish between v3.1 and v3.10 #29731 [3.10] bpo-45616: Let py.exe distinguish between v3.1 and v3.10 (GH-29731) #29740

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2021-11-24.17:58:01.257>
created_at = <Date 2021-10-26.17:51:14.935>
labels = ['type-bug', '3.10', 'OS-windows', '3.11']
title = 'Python Launcher Matches 3.10 instead of 3.1'
updated_at = <Date 2021-11-24.17:58:01.256>
user = 'https://github.com/Marsfan'

bugs.python.org fields:

activity = <Date 2021-11-24.17:58:01.256>
actor = 'zach.ware'
assignee = 'none'
closed = True
closed_date = <Date 2021-11-24.17:58:01.257>
closer = 'zach.ware'
components = ['Windows']
creation = <Date 2021-10-26.17:51:14.935>
creator = 'Marsfan'
dependencies = []
files = []
hgrepos = []
issue_num = 45616
keywords = ['patch']
message_count = 4.0
messages = ['405054', '406901', '406902', '406943']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'steve.dower', 'miss-islington', 'Marsfan']
pr_nums = ['29731', '29740']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45616'
versions = ['Python 3.10', 'Python 3.11']

[Marsfan]

I have both Python 3.1-64 and 3.10-64 installed on the same Windows machine. If I attempt to launch Python 3.1 using the command py -3.1-64, the launcher incorrectly starts Python 3.10.

[zware]

New changeset f9de97a by Zachary Ware in branch 'main':
bpo-45616: Let py.exe distinguish between v3.1 and v3.10 (GH-29731)
f9de97a

[miss-islington]

New changeset ae065f8 by Miss Islington (bot) in branch '3.10':
bpo-45616: Let py.exe distinguish between v3.1 and v3.10 (GH-29731)
ae065f8

[zware]

Thanks for the report, Gabe! We actually ran into this in the opposite direction as well; a system with 3.1 but not 3.10 started up 3.1 for py -3.10 causing unexpected syntax errors.

The fix is now merged and will be available with the release of v3.10.1 and the next v3.11 alpha.