-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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] Python build was broken by Cython 3.0.9 #40386
Comments
Note that this is causing all benchmarking builds to fail as well (causing messages like #40367 (comment)) |
Duplicated of #40375. |
### Rationale for this change See #40386, these changes are necessary for compatibility with Cython 3.0.9 ### What changes are included in this PR? This PR removes unnecessary `noexcept` clauses. ### Are these changes tested? Covered by existing builds. ### Are there any user-facing changes? No. * GitHub Issue: #40386 Authored-by: Vyas Ramasubramani <[email protected]> Signed-off-by: Felipe Oliveira Carvalho <[email protected]>
### Rationale for this change See apache#40386, these changes are necessary for compatibility with Cython 3.0.9 ### What changes are included in this PR? This PR removes unnecessary `noexcept` clauses. ### Are these changes tested? Covered by existing builds. ### Are there any user-facing changes? No. * GitHub Issue: apache#40386 Authored-by: Vyas Ramasubramani <[email protected]> Signed-off-by: Felipe Oliveira Carvalho <[email protected]>
Closed by #40387 |
Small follow-up, we indeed do that here: Lines 722 to 723 in 49cdb0f
(I was wondering myself as well ;)) And thanks for the PR! |
Aha I didn't realize it was building with CMake using a custom setuptools command setup. My follow-up was going to be if you'd considered using scikit-build, but it looks like there's already discussion of that in #36411! |
### Rationale for this change See apache#40386, these changes are necessary for compatibility with Cython 3.0.9 ### What changes are included in this PR? This PR removes unnecessary `noexcept` clauses. ### Are these changes tested? Covered by existing builds. ### Are there any user-facing changes? No. * GitHub Issue: apache#40386 Authored-by: Vyas Ramasubramani <[email protected]> Signed-off-by: Felipe Oliveira Carvalho <[email protected]>
### Rationale for this change See #40386, these changes are necessary for compatibility with Cython 3.0.9 ### What changes are included in this PR? This PR removes unnecessary `noexcept` clauses. ### Are these changes tested? Covered by existing builds. ### Are there any user-facing changes? No. * GitHub Issue: #40386 Authored-by: Vyas Ramasubramani <[email protected]> Signed-off-by: Felipe Oliveira Carvalho <[email protected]>
Describe the bug, including details regarding any error messages, version, and platform.
The Cython 3.0.9 release yesterday (3/5/24) added a warning when a Cython function is marked noexcept while returning a Python object. This appears to have broken builds of pyarrow (see recent runs on #40373). I glanced at pyarrow's setup.py and it wasn't immediately obvious clear where/if pyarrow is setting warnings as errors for Cython, but I assume it is doing so if it's breaking the build.
Component(s)
Python
The text was updated successfully, but these errors were encountered: