-
Notifications
You must be signed in to change notification settings - Fork 267
Add compatibility for Pyodide-tagged wheels #804
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
Open
hoodmane
wants to merge
6
commits into
pypa:main
Choose a base branch
from
hoodmane:pyodide-compat
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
cf62f7f
Add Pyodide compatibility
hoodmane 51712d7
Merge branch 'main' into pyodide-compat
brettcannon bf66c63
Merge branch 'main' into pyodide-compat
hoodmane 5d5b76d
Add tests
hoodmane c18c884
Merge branch 'main' into pyodide-compat
hoodmane ee80f3a
Fix tests
hoodmane File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this really yield the generic platform here as well, or is an
else
missing, so that_generic_platforms
is yielded similar to the fallback inplatform_tags
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this is correct as is, since you want to also be able to match
emscripten_...
tags.pyodide
is just a more specific tag.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I've understood @hoodmane's recent work correctly, all our forthcoming tags will be labelled with
pyodide_YYYY_N
as per the Pyodide ABI information at https://pyodide.org/en/stable/development/abi.html#pyodide-2025-0-under-development and with PEP 783: https://peps.python.org/pep-0783/#specification thatpackaging
will implement through this PR. I think the distinction is important, asemscripten
is no longer the same aspyodide
since2025_0
. In 2024, one could have both2024_0
andemscripten_3_1_58
, which meant the same thing.2025_0
does not have anemcripten_4_0_9
equivalent.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should keep it as is because
emscripten_4_0_9
is the name of the platform and so it's the default tag. If anyone has wheels with this platform it makes sense to accept them.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, okay to keep it if you say so! :)