Windows py launcher: older 32-bit versions not supported in some cases #101135
Labels
Comments
|
Note that I currently have a fix on the way, which also fixes some related issues in the way the |
boimart1
added a commit
to boimart1/cpython
that referenced
this issue
Jan 18, 2023
For 32-bit installs, these versions did not contain the "-32" in their registry name, so the 32 and 64-bit installs were treated equal. Additionally, the code to replace a node with one with a lower sort key was buggy (wrong node chosen, replace never happened since parent was always NULL, replaced node never freed, etc)
zooba
pushed a commit
that referenced
this issue
Jan 24, 2023
…32-bit versions (GH-101138) Python 2.x and up to 3.4 did not contain the "-32" in their registry name, so the 32 and 64-bit installs were treated equal. Since 3.5/PEP 514 this is no longer true, but we still want to detect the EOL versions correctly in case people are still using them. Additionally, the code to replace a node with one with a lower sort key was buggy (wrong node chosen, replace never happened since parent was always NULL, replaced node never freed, etc)
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jan 24, 2023
…older 32-bit versions (pythonGH-101138) Python 2.x and up to 3.4 did not contain the "-32" in their registry name, so the 32 and 64-bit installs were treated equal. Since 3.5/PEP 514 this is no longer true, but we still want to detect the EOL versions correctly in case people are still using them. Additionally, the code to replace a node with one with a lower sort key was buggy (wrong node chosen, replace never happened since parent was always NULL, replaced node never freed, etc) (cherry picked from commit daec3a4) Co-authored-by: Martin Boisvert <[email protected]>
miss-islington
added a commit
that referenced
this issue
Jan 24, 2023
…32-bit versions (GH-101138) Python 2.x and up to 3.4 did not contain the "-32" in their registry name, so the 32 and 64-bit installs were treated equal. Since 3.5/PEP 514 this is no longer true, but we still want to detect the EOL versions correctly in case people are still using them. Additionally, the code to replace a node with one with a lower sort key was buggy (wrong node chosen, replace never happened since parent was always NULL, replaced node never freed, etc) (cherry picked from commit daec3a4) Co-authored-by: Martin Boisvert <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
On 64-bit Windows, if both Python 2.7 32-bit and Python 2.7 64-bit are installed, these two installs are considered equivalent and only the 64-bit version is considered, both when running
py -2-32(which fails) andpy -0(which only displays the 64-bit version).This is also the case for Python 3.4 and lower, as the "-32" suffix is only part of the tag in the registry in 3.5+.
Under
C:\:py -0poutput:While these versions are no longer officially supported since 2020, PEP-514 does have a section on backwards compatibility, mentioning:
Your environment
Linked PRs
The text was updated successfully, but these errors were encountered: