jorisvandenbossche commented on issue #35531: URL: https://github.com/apache/arrow/issues/35531#issuecomment-1737802944
Pinging some people from libraries that currently already do use the Arrow C Data interface to consume (or produce) arrow data, and currently typically use the `_export_to_c` method to get the C struct pointers. Since this proposal is exactly for those use cases (and long term ideally people move to use this protocol instead of relying on the pyarrow-specific `_export_to_c`), letting you know in case you have feedback on the general proposal (see the `PyCapsuleInterface.rst` file in the PR https://github.com/apache/arrow/pull/37797 for the most up to date description), or if you see any potential problem in adopting this. cc @Mytherin @pdet for duckdb, you currently call `_export_to_c` on pyarrow objects in your C++ code, that could be replaced by this protocol (and then also wouldn't be limited to pyarrow objects) @wjones127 it seems you have been recently committing to the arrow-rs code that does this conversion (https://github.com/apache/arrow-rs/blob/master/arrow/src/pyarrow.rs) @xwu99 for xgboost using the C interface to support Arrow data (https://github.com/dmlc/xgboost/commit/613ec36c5a552363b348854a5765aad52b403c52) @ritchie46 for polars (https://github.com/pola-rs/polars/blob/main/py-polars/src/arrow_interop/to_rust.rs and https://github.com/pola-rs/pyo3-polars/blob/main/pyo3-polars/src/ffi/to_rust.rs) @amunra for py-questdb-client (https://github.com/questdb/py-questdb-client/blob/4584366f6afafcdac4f860354c48b78da8589eb4/src/questdb/dataframe.pxi#L808) Some other places where we also want to update this in the Arrow projects itself are nanoarrow, adbc, the R package, arrow-rs. -- 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]
