Skip to content
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

Separate pyo3 arrow integration into standalone crate #6776

Open
xmakro opened this issue Nov 22, 2024 · 1 comment
Open

Separate pyo3 arrow integration into standalone crate #6776

xmakro opened this issue Nov 22, 2024 · 1 comment
Labels
enhancement Any new improvement worthy of a entry in the changelog

Comments

@xmakro
Copy link
Contributor

xmakro commented Nov 22, 2024

The pyo3 crate released version 0.23. The arrow crate depends on pyo3 0.22 and it is not possible for arrow to update the pyo3 dependency without a major breaking release. Therefore, it is currently not possible for a user to upgrade a codebase that depends both on arrow and pyo3.

To fix this, we could instead move the arrow pyo3 integration into a separate crate. This crate could then be updated to a new version of pyo3 outside of the arrow major release cadence. Since it is a separate crate, it would require wrapper structs around structs that implement IntoPyObject.

@xmakro xmakro added the enhancement Any new improvement worthy of a entry in the changelog label Nov 22, 2024
@tustvold
Copy link
Contributor

The next arrow release, due in December will be breaking and incorporate this version upgrade. We make breaking releases at most every 3 months, looking at the history of pyo3 breaking releases, this shouldn't lead to that much of a lag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Any new improvement worthy of a entry in the changelog
Projects
None yet
Development

No branches or pull requests

2 participants