Update vaex version ranges #2438
Closed
Conversation
This file contains 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
|
cc @maartenbreddels for when the universal packages (except |
|
Ah, I don't think this is needed. I've build this release script (which already noticed vaex-hdf5 requires releasing) which will then auto bump this range. But now I understand what you meant. (Yes, vaex-core should be redone, but locally it looks like it was released) |
|
ah nice! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
awaiting upcoming cp312 support releases ref #2331 (comment)
this PR also prevents dephell for users who go
pip install vaexinto an existing environment, leading pip to potentially choose older versions of the universal packages