-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Python][Packaging] Support Python 3.13 and upload wheels #43519
Comments
I was planning, if necessary, to delay the feature freeze for 18.0.0 for a week to have Python 3.13 wheels. |
We can actually make wheels right now (and we should ideally produce nightly wheels well before the scheduled release of 18.0), because Python 3.13 is ABI stable now, and wheels built with the current Python 3.13 will work with the final 3.13 releases. (so there is certainly no need to delay 18.0.0 AFAIK) |
Follow-ups after #43539:
EDIT: added those to the top post |
### Rationale for this change Like #43519 mentionies, now that the first `rc` is out, it's probably time to add CI coverage for Python 3.13 (and also start building wheels). ### What changes are included in this PR? I'm fairly new to the build/CI processes of the project, but I tried to follow the same template as #37901. I'll follow up afterwards with adding CI coverage for the free-threaded build as well. * GitHub Issue: #43519 Lead-authored-by: Lysandros Nikolaou <[email protected]> Co-authored-by: Joris Van den Bossche <[email protected]> Signed-off-by: Joris Van den Bossche <[email protected]>
…e#43539) ### Rationale for this change Like apache#43519 mentionies, now that the first `rc` is out, it's probably time to add CI coverage for Python 3.13 (and also start building wheels). ### What changes are included in this PR? I'm fairly new to the build/CI processes of the project, but I tried to follow the same template as apache#37901. I'll follow up afterwards with adding CI coverage for the free-threaded build as well. * GitHub Issue: apache#43519 Lead-authored-by: Lysandros Nikolaou <[email protected]> Co-authored-by: Joris Van den Bossche <[email protected]> Signed-off-by: Joris Van den Bossche <[email protected]>
…d and test wheels on Python 3.13
…nup-requirements
…nup-requirements
Python 3.13 is scheduled for Monday (10/7). Would it be possible to make a 18.0.0b0 or 18.0.0rc0 release on PyPI in the near future? I know you have wheels on https://anaconda.org/scientific-python-nightly-wheels/pyarrow/files, but having a pre-release on PyPI would make it easier for projects that aren't aware of the "nightly" wheels. |
I've installed today the v3.13 of Python, and it's affected by this pyarrow issue. |
According to https://discuss.python.org/t/launch-day-availability-of-python-3-13-in-conda-forge/67124/1, 3.13 is now available in conda-forge. |
Yes, please wait for 18.0.0 which will provide binary wheels for 3.13. |
…nup-requirements
…instead of Release Candidates
…test wheels on Python 3.13 (#44193) ### Rationale for this change Now that numpy, cython and pandas all have releases that support Python 3.13, we can remove the extra index and ensure that we are building our wheels with the released version instead of nightly dev version. * GitHub Issue: #43519 Authored-by: Joris Van den Bossche <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
…test wheels on Python 3.13 (#44193) ### Rationale for this change Now that numpy, cython and pandas all have releases that support Python 3.13, we can remove the extra index and ensure that we are building our wheels with the released version instead of nightly dev version. * GitHub Issue: #43519 Authored-by: Joris Van den Bossche <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
…instead of Release Candidates
### Rationale for this change When adding Python 3.13 support (#43539), conda was not yet ready to support Python 3.13. But over the last weeks most conda packages having being updated, so trying again. * GitHub Issue: #43519 Authored-by: Joris Van den Bossche <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
### Rationale for this change When adding Python 3.13 support (#43539), conda was not yet ready to support Python 3.13. But over the last weeks most conda packages having being updated, so trying again. * GitHub Issue: #43519 Authored-by: Joris Van den Bossche <[email protected]> Signed-off-by: Raúl Cumplido <[email protected]>
The only missing task if to update to the final released version of Python (we are just waiting for chocolatey or to migrate out of chocolatey).
|
Wow - I was not aware it takes chocolatey more than a week to update the latest stable Python version. Considering that there are packages whose 3.13 support depends on arrow's, maybe you want to consider scoop in the future, which updated a week ago: ScoopInstaller/Main@ec70b27 |
Given this issue is closed, where should I subscribe to make sure I am aware when pyarrow that is compatible is Python 3.13 is actually released? Thanks! |
@pllim you can subscribe to the PyPI feed: https://pypi.org/rss/project/pyarrow/releases.xml |
Wheels for Python 3.13 have been uploaded to PyPI |
Python 3.13 is currently in a prerelease status (a first release candidate was released today: https://discuss.python.org/t/python-3-13-0-release-candidate-1-released/59703) and is expected to have a final release in October this year (https://devguide.python.org/versions).
We should ensure we are fully ready to support Python 3.13 for the PyArrow 18 release that will happen around the same time (or potentially even sooner if we would have a 17.0.x bug fix release).
#42034 already fixed a build issue with Python 3.13, and on the short term I think we should try to have 1) a CI build using Python 3.13 to ensure this keeps working, and 2) set up a wheel build so we can upload nightly wheels for Python 3.13 for downstream testing.
(equivalent PR for Python 3.12: #37901)
arrow/dev/tasks/tasks.yml
Lines 1200 to 1201 in 712cfe6
requirements-wheel-build.txt
andrequirements-wheel-test.txt
to install released versionsinstall_gcs_testbench.sh
) (or address GH-38183 and install testbench with independent python version)The text was updated successfully, but these errors were encountered: