Use the -embeddable Python download rather than -embed. - #3044
Merged
Conversation
Member
Author
|
@mhsmith Tagging for visibility; needed to merge this to get a release out. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Python.org offers 2 "embeddeable" downloads for each version/architecture:
The public download page uses the former; but the
windows.jsonrelease manifest only includes the latter. The release manifest includes release hashes; hashes for the -embed variants are on the website, but nowhere else.The contents of the files are identical, except for a single
__install__.jsonfile in the-embeddablevariant that includes some useful metadata.Since we need to be able to easily verify hashes, we should use the version that has readily available published hashes.
PR Checklist: