[sundeep8967]

Rationale for this change

The Python documentation explains the PyCapsule Interface (__arrow_c_schema__, __arrow_c_array__, __arrow_c_stream__), but lacks an ecosystem implementation status table showing which libraries have adopted the protocol. Issue #47696 requested adding an implementation status table based on tracking in #39195.

Per maintainer feedback in #47696 and PR #49550, every single listed library has been individually audited and updated against its upstream repository and latest release status rather than simply copying the initial table snapshot:

• Audit & Status updates: Updated libraries that have implemented or merged support (e.g. Daft in feat: Arrow PyCapsule Interface Eventual-Inc/Daft#6745, Vortex in feat(python): Write PyArrow types directly to Vortex vortex-data/vortex#4161, Xarray in feat: add __arrow_c_stream__ function pydata/xarray#11338, Streamlit in Add support for PyCapsule streamlit/streamlit#13242, PySpark in [SPARK-54337][PS] Add support for PyCapsule to Pyspark spark#53391).
• Added missing implementations: Added libraries from community contributions in [Python] Promote usage of the Arrow PyCapsule Protocol (for the C Data Inteface) #39195 including streamlit, jupyter-scatter, pyfru, and minarrow.
• Accurate direct links: Linked directly to official documentation or merged implementation PRs (such as arro3 docs instead of raw issue comments).
• Alphabetical sorting and clean format: Uses an alphabetical .. list-table:: with checkmarks (✓ / ✗).

What changes are included in this PR?

• Added a comprehensive PyCapsule Interface Implementation Status table containing 33 ecosystem libraries to docs/source/python/extending_types.rst.
• Linked each library directly to its implementation PR, issue, or documentation.

Are these changes tested?

Documentation-only change. ReStructuredText syntax validated with docutils.

Are there any user-facing changes?

Yes, a new "PyCapsule Interface Implementation Status" reference table is visible in the Python documentation under the "Extending PyArrow" section.

Was AI used for this PR?

In accordance to the AI generation guidelines, please disclose below whether and how AI was used in this PR.

PR code and description written by:

• Human
• AI

Reviewed before submission by:

• Human
• AI
• Not reviewed

---

Fixes #47696

• GitHub Issue: [Docs][Python] PyCapsule protocol implementation status #47696

[github-actions]

⚠️ GitHub issue #47696 has been automatically assigned in GitHub to PR creator.

[AlenkaF]

PR template has been overwritten by your agent. Use the PR template provided by the project and specify if you (human) checked the constructed table and links.

Note the review process might be slow due to huge backlog of PRs at the moment.

[sundeep8967]

Hi @AlenkaF,

Thank you for pointing that out! I have updated the PR description to strictly adhere to the official Apache Arrow PR template, including the AI disclosure section.

To confirm: I have personally verified each of the 33 entries and their respective target URLs, ensuring all links resolve to valid, active documentation pages or merged implementation PRs/issues (e.g., verifying Daft #6745, Vortex #4161, Xarray #11338, Streamlit #13242, and arro3 docs).

Thank you for your review and patience!