Skip to content

[Python] Deprecate Feather reader and writer #49232

Description

@pitrou

Describe the enhancement requested

See #49231 for rationale.

As for the C++ side, we could deprecate the reader and writer at the same time but schedule their respective removals at different times.

Component(s)

Python

Activity

  1. pitrou commented on Feb 11, 2026

    @pitrou
    MemberAuthor
  2. piyushka-ally commented on Mar 23, 2026

    @piyushka-ally
    Contributor

    Hey, would it be okay if I tackle this issue?

  3. raulcd commented on Mar 23, 2026

    @raulcd
    Member

    @piyushka-ally sure, I've assigned you the issue

  4. added a commit that references this issue on Mar 24, 2026
  5. piyushka-ally commented on Mar 29, 2026

    @piyushka-ally
    Contributor

    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!

  6. AlenkaF commented on Jul 1, 2026

    @AlenkaF
    Member

    @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?

  7. pitrou commented on Jul 1, 2026

    @pitrou
    MemberAuthor

    +1 for merging this without waiting.

  8. added this to the 25.0.0 milestone on Jul 1, 2026
  9. added a commit that references this issue on Jul 1, 2026
  10. 15 remaining items

  11. rok commented on Jul 30, 2026

    @rok
    Member

    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 :)

  12. added 7 commits that reference this issue on Aug 3, 2026
  13. added a commit that references this issue on Aug 4, 2026
  14. tadeja commented on Aug 4, 2026

    @tadeja
    Member

    Follow-up moved to the new issue GH-50808/ PR #50685 targeted for 25.0.1 with both changes:

    1. Feather V2 reader/writer APIs will no longer emit the deprecation warnings introduced in 25.0.0
    2. Legacy Feather V1 will emit DeprecationWarning instead of FutureWarning used in 25.0.0
  15. added 5 commits that reference this issue on Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions