-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-96729: Ensure upgradability between official and buildrelease.bat releases #96755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
As of ce21a9b, Windows installations created using buildrelease.bat cannot be used to upgrade to/from official Python installations. Official Python releases use a RELEASE_URI with a scheme of http, while buildrelease.bat was changed to use a RELEASE_URI with a scheme of https. This changes the value in buildrelease.bat to match that of official releases.
Thanks @adang1345 for the PR, and @zooba for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11. |
…at have matching UUIDs with official releases (pythonGH-96755) (cherry picked from commit 662782e) Co-authored-by: adang1345 <[email protected]>
GH-96774 is a backport of this pull request to the 3.11 branch. |
GH-96775 is a backport of this pull request to the 3.10 branch. |
…at have matching UUIDs with official releases (pythonGH-96755) (cherry picked from commit 662782e) Co-authored-by: adang1345 <[email protected]>
Thanks for the fix! I'm backporting this, because it's most important for people building old releases with additional patches. (It won't be in 3.11.0, but that's fine) |
…e matching UUIDs with official releases (GH-96755) (cherry picked from commit 662782e) Co-authored-by: adang1345 <[email protected]>
…e matching UUIDs with official releases (GH-96755) (cherry picked from commit 662782e) Co-authored-by: adang1345 <[email protected]>
…e matching UUIDs with official releases (GH-96755) (cherry picked from commit 662782e) Co-authored-by: adang1345 <[email protected]>
See details at #96729