Set an upper bound for numpy to dodge 2.0 #1963
Merged
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
ihnorton
approved these changes
May 10, 2024
|
@kounelisagis does this look okay to you? |
kounelisagis
approved these changes
May 10, 2024
kounelisagis
pushed a commit
that referenced
this pull request
Jun 17, 2024
* Set an upper bound for numpy to dodge 2.0 * Add missing trailing commas * Fix list of spec strings (cherry picked from commit 19bc046)
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.
Set an upper bound for numpy to dodge 2.0 and avoid incompatible upcoming release until we support it. x-ref sc-46950
[sc-47060]