Fixing the artifact generation to use the right Python versions#157
Merged
Conversation
Collaborator
|
@ciaranra would it be better to be using abi3 wheels targeting Python 3.10 and above instead of generating wheels for each Python version? That's what we are doing for several internal packages. |
Member
Author
|
Maybe, not sure what that is. Will look into it, thanks! |
Member
Author
|
I guess that is a particular binary interface for Python that maybe works for different versions? If so... didn't know you could generate one wheel for PyO3 for, e.g., Python 3.10+, nice |
…stallation/import per supported Python versions
Member
Author
|
Alright cool. That works. Thanks for pointing that out @qartik! |
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
2 participants
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.
No description provided.