-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
build(python): Officially support Python 3.13 #20549
base: main
Are you sure you want to change the base?
Conversation
The previous uncompressed lib size was Unknown MB. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #20549 +/- ##
==========================================
- Coverage 79.05% 78.98% -0.08%
==========================================
Files 1564 1564
Lines 220627 220759 +132
Branches 2502 2504 +2
==========================================
- Hits 174413 174358 -55
- Misses 45640 45827 +187
Partials 574 574 ☔ View full report in Codecov by Sentry. |
uv pip install -U typing-extensions | ||
uv pip install --compile-bytecode -r requirements-dev.txt -r requirements-ci.txt --verbose | ||
uv pip install -U typing-extensions | ||
uv pip install --compile-bytecode -r requirements-dev.txt -r requirements-ci.txt --verbose --index-strategy=unsafe-best-match |
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.
The --extra-index-url https://download.pytorch.org/whl/cpu
entry in requirements-ci.txt
caueses issues for NumPy installation under Python 3.13. Specifying this index strategy makes it so that NumPy is downloaded from the regular PyPI registry rather than the PyTorch registry.
Polars was already installable under Python 3.13 and already worked. This PR officially marks Python 3.13 as supported and updates our CI to also run tests under Python 3.13.
There's still some issue with the benchmark workflow due to the setup of our self-hosted runner. We can look into this later.
There's also an issue with running MyPy with the latest NumPy version that came up because of this PR. I made an issue for this: #20561