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.
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
Add support for Python 3.13 #3490
Add support for Python 3.13 #3490
Changes from 8 commits
f7462f6
92d5945
bfcec3a
f545e17
40545a0
47eaad8
642a538
6e74524
a06f906
ada48f3
90d9b42
f9fa6d7
742980e
df35168
93273cd
631444f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Since we're including PyArrow in the Python 3.11 CI build as of #3605, let's just remove PyArrow here until it supports Python 3.13 to not hold up #3606?
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.
We can't remove PyArrow in the Python 3.13 job, because we need both pandas<2.2+pyarrow (in Python 3.11) and pandas>=2.2+pyarrow (in Python 3.12 or 3.13) to test the behavior changes in pands 2.2.
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 was thinking we could do (after #3606) Python 3.11+pandas=2.1+pyarrow; Python 3.12+pandas=2.2+pyarrow, but anyways, this won't work yet because
mamba install
is still complaining about some incompatible depedencies (looks like something ondvc
):Wait for conda-forge/python-gssapi-feedstock#32.
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.
Also need to wait for conda-forge/kombu-feedstock#78:
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.
conda-forge/python-gssapi-feedstock#32 has been superseded by conda-forge/python-gssapi-feedstock#33.
So we still need to wait for conda-forge/kombu-feedstock#78. kombu's Python 3.13 support was added in celery/kombu#2052, which first appeared in kombu v5.5.0rc2.
kombu v5.5.0rc2 was released two months ago, and there is still no kombu v5.5.0 out. Not sure how long we have to wait.
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.
Ok, for reference, we applied a workaround for
dvc
in #3695, andpyarrow
now has a Python 3.13 build since conda-forge/pyarrow-feedstock#139.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.
Note that this has changed from
python=3.12
topython>=3.10
to folllow SPEC 0 (same with NumPy, pandas and xarray lines below).