tadeja commented on issue #49232: URL: https://github.com/apache/arrow/issues/49232#issuecomment-5105290467
@jorisvandenbossche @raulcd @pitrou @rok would it make sense to rework #49590 to deprecate strictly V1 format instead of whole`pyarrow.feather` API and potentially include this in the 25.0 RC/patch release? > The linked email list thread in [#49231](https://github.com/apache/arrow/issues/49231) seems to be specific about deprecating the "Feather V1" reader/writer. And I definitely agree with deprecating V1, but the `pyarrow.feather` APIs are also used (and actually write that by default) to read/write the "Feather V2" / Arrow IPC file format, which is not deprecated. For discussion here I've put up a prototype https://github.com/apache/arrow/pull/50685 with the help of AI :robot: Fable. > (also, in the future, we should ideally do such deprecations with a DeprecationWarning first, before using a FutureWarning, to avoid users seeing this through downstream packages) ( Here's orthogonal test prototype using `DeprecationWarning` in place of current `FutureWarning` https://github.com/apache/arrow/pull/50686 ) -- 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]
