You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Python] Deprecate Feather reader and writer #49232
Could a maintainer please add the Component: Python label to this issue? The CI bot is flagging the associated PR (#49590) for missing component labels. Thanks!
@pitrou the linked PR that deprecates Feather reader and writer in PyArrow can be merged if we agree Python deprecation gets merged before C++ does (I think there is no PR yet for C++?). Otherwise I can tackle the C++ deprecation when I get a chance and we merge Python and C++ together. What do you think?
Sounds pretty unambiguous and clear to me what this is supposed to do. Should we create a new issue? we can discuss exact method naming and UX on the issue or in a possible PR?
Let's split deprecation into issue/PR and continue name here and on ML? There was already some discussion there that we don't need to reinvent :)
Activity
pitrou commentedon Feb 11, 2026
@AlenkaF @rok
piyushka-ally commentedon Mar 23, 2026
Hey, would it be okay if I tackle this issue?
raulcd commentedon Mar 23, 2026
@piyushka-ally sure, I've assigned you the issue
apacheGH-49232: [Python] Deprecate Feather reader and writer
piyushka-ally commentedon Mar 29, 2026
Could a maintainer please add the
Component: Pythonlabel to this issue? The CI bot is flagging the associated PR (#49590) for missing component labels. Thanks!AlenkaF commentedon Jul 1, 2026
@pitrou the linked PR that deprecates Feather reader and writer in PyArrow can be merged if we agree Python deprecation gets merged before C++ does (I think there is no PR yet for C++?). Otherwise I can tackle the C++ deprecation when I get a chance and we merge Python and C++ together. What do you think?
pitrou commentedon Jul 1, 2026
+1 for merging this without waiting.
GH-49232: [Python] deprecate feather python (#49590)
15 remaining items
rok commentedon Jul 30, 2026
Let's split deprecation into issue/PR and continue name here and on ML? There was already some discussion there that we don't need to reinvent :)
apacheGH-49232: [Python] Add IPC aliases for Feather APIs
apacheGH-49232: [Python] Point Feather users to IPC aliases
apacheGH-49232: [Python] Use DeprecationWarning for Feather APIs
apacheGH-49232: [Python] Add IPC aliases for Feather APIs
apacheGH-49232: [Python] Point Feather users to IPC aliases
apacheGH-49232: [Python] Use DeprecationWarning for Feather APIs
GH-50808: [Python] Narrow Feather deprecation to V1 format (#50685)
GH-50808: [Python] Narrow Feather deprecation to V1 format (#50685)
tadeja commentedon Aug 4, 2026
Follow-up moved to the new issue GH-50808/ PR #50685 targeted for 25.0.1 with both changes:
DeprecationWarninginstead ofFutureWarningused in 25.0.0apacheGH-49232: [Python] Add high-level IPC file functions
apacheGH-49232: [Python] Add high-level IPC file functions
apacheGH-49232: [Python] Add high-level IPC file functions
apacheGH-49232: [Python] Add high-level IPC file functions
apacheGH-49232: [Python] Add high-level IPC file functions