aljazerzen commented on issue #5368:
URL: https://github.com/apache/arrow-rs/issues/5368#issuecomment-2074666857
Unfortunately, I agree that because of the bump of `pyo3` (and maybe
`object_store`, didn't check), `arrow` needs a major version bump as well.
This will create a lot of toll downstream, because crates use arrow types in
their public interfaces so they will face same problems as arrow is facing with
pyo3. It is a shame that the whole `arrow` crate needs to be bumped only for
pyo3 (which might not even be enabled in some dependencies).
---
If I understand the "semver-trick" this would be the release process:
- publish arrow 52.0 as normal,
- publish arrow 51.1, with dependency on arrow 52.0 and lib.rs looking
something like this:
```rust
pub use arrow::buffer; // reexport from arrow 52.0
mod pyarrow; // this would still be using the old version of pyo3
```
This would also mean that most of the code in arrow 51.1 could be removed
and just replaced with dependencies on arrow 52.
This is all way too much work, while also not solving the problem of
publishing the new major versions. It would just make lagging behind the latest
arrow version less of a problem because old versions would contain most of the
new changes.
---
Another solution would be to move pyarrow module into a separate crate that
can be versioned independently.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
