Conversation
…til they ship 3.15 wheels.
|
|
|
@github-actions crossbow submit wheel-manylinux-2-28-cp315-cp315-amd64 |
|
Revision: 2d2a557 Submitted crossbow builds: ursacomputing/crossbow @ actions-c8d038a747
|
|
The build was destined for failure, because cp315 is not yet in the manylinux build. I'll reproduce locally and see if there's a graceful way to resolve, along with a clearer failure when PYTHON_ROOT is not found. The build failed oddly, but the earlier issue was that the detection of PYTHON_ROOT failed quietly:
A test should be added to verify PYTHON_ROOT is set / not empty and fail fast: arrow/ci/docker/python-wheel-manylinux.dockerfile Lines 110 to 111 in 2fb2f79 Build FailureCrossbow failed due to
caused by
|
|
Looking more closely, and considering the history of 3.13 and 3.14: This (nightlys) needs to wait manylinux adds cp315. The alternative is to add a cpython build step or use one of the other pre-built images, but this seems like more work than other projects are investing at this stage. Based on history of 3.13/3.14, this would be after b1 / 2026-05-05. |
Rationale for this change
Add Python 3.15 to the pyarrow nightly builds, so that issues can be detected early in the development cycles of both cpython & pyarrow.
Note:
What changes are included in this PR?
Are these changes tested?
ninja-release-pythonpreset (not maximal)Are there any user-facing changes?
No functional changes, other than allowing the user to use Python 3.15.