Remove the upper bound constraint on python version #7949
Merged
+12
−3
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.
What
We previously had this constraint in place to avoid certain edge cases of users not being able to install Rerun and not understanding why due to transitive deps. Primarily on pyarrow.
I've confirmed pyarrow is now doing something similar in their own project:
https://github.com/apache/arrow/blob/main/python/pyproject.toml#L37
Let's try to let the package solver do the right thing and only add a max-version if we find we are truly incompatible with some future python version.
Checklist
main
build: rerun.io/viewernightly
build: rerun.io/viewerCHANGELOG.md
and the migration guideTo run all checks from
main
, comment on the PR with@rerun-bot full-check
.