piyushka-ally opened a new pull request, #49590:
URL: https://github.com/apache/arrow/pull/49590

   ### Rationale for this change
   
   Arrow C++ is deprecating the Feather reader/writer (#49231) so we should 
update the Python functions too. Feather V2 is exactly the Arrow IPC file 
format, making the separate `pyarrow.feather` module redundant. Users should 
migrate to `pyarrow.ipc`.
   
   ### What changes are included in this PR?
   
   - Added `FutureWarning` deprecation warnings to all four public APIs in 
`pyarrow.feather`: `write_feather()`, `read_feather()`, `read_table()`, and 
`FeatherDataset`
   - Extracted `_read_table_internal()` so that `read_feather()` calling 
`read_table()` internally does not produce double warnings
   - Updated `FeatherDataset.read_table()` to use the internal function for the 
same reason
   - Added `.. deprecated:: 24.0.0` directives to all four public API docstrings
   - Added module-level `pytestmark` filter in `test_feather.py` to suppress 
warnings in existing tests
   - Added 5 new tests verifying deprecation warnings are emitted correctly 
(including a no-double-warning test)
   - Added `@pytest.mark.filterwarnings` to 5 test functions in 
`test_dataset.py` that use feather as a utility
   - Updated `feather.rst` with a deprecation notice and migration guide 
(including a note that `pyarrow.ipc` does not compress by default unlike 
`feather.write_feather`)
   - Updated `formats.rst` to mark the Feather API section as deprecated
   
   ### Are these changes tested?
   
   Yes. Five new tests verify that each deprecated function emits exactly one 
`FutureWarning`, and existing tests continue to pass with module/function-level 
warning filters.
   
   ### Are there any user-facing changes?
   
   Yes — calling `pyarrow.feather.write_feather()`, `read_feather()`, 
`read_table()`, or `FeatherDataset()` now emits a `FutureWarning` directing 
users to `pyarrow.ipc` equivalents. Existing functionality is unchanged.
   


-- 
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]

Reply via email to