GitHub user dangotbanned added a comment to the discussion: A new home for pyarrow-stubs?
## Easing maintenance burden > [!NOTE] > TL;DR: If downstream users feel confident they can contribute *typing-only* > changes, they'll be able to spread the burden 🙂 How the stubs/inline typing can be maintained in a sustainable way, seems to have been *a* concern of most voices here: <details><summary><b>Show related comments</b></summary> <p> - https://github.com/apache/arrow/discussions/45919#discussioncomment-14209115 - https://github.com/apache/arrow/discussions/45919#discussioncomment-14245807 - https://github.com/apache/arrow/discussions/45919#discussioncomment-14246287 - https://github.com/apache/arrow/discussions/45919#discussioncomment-14275681 - https://github.com/apache/arrow/discussions/45919#discussioncomment-14295165 - https://github.com/apache/arrow/discussions/45919#discussioncomment-14296726 - https://github.com/apache/arrow/discussions/45919#discussioncomment-14297417 - https://github.com/apache/arrow/discussions/45919#discussioncomment-14385023 </p> </details> While there is [Writing and Maintaining Stub Files](https://typing.python.org/en/latest/guides/writing_stubs.html) to refer to for guidance, both that document and (I assume) the discussion so far have been asking/answering: > How can the *current* maintainers of `pyarrow`, maintain the stubs? That is an important question, but I think making the process *sustainable* may benefit from answering this question as well: > How can the *current* maintainers of `pyarrow`, make it easy/easier for > downstream users to **contribute to** the stubs? I can only speak to my own experience, so as an example ... ### Example story I feel confident in [identifying](https://github.com/narwhals-dev/narwhals/issues/2124#issue-2889033104) when there are issues in stubs, even if that requires [*reading* a lil bit of `cython`](https://github.com/apache/arrow/pull/47609#pullrequestreview-3286217370) I also think I have *enough* of an understanding of the [python typing spec](https://typing.python.org/en/latest/spec/index.html) to propose changes which [utilize](https://github.com/zen-xu/pyarrow-stubs/pull/215/files) new features as they land. I feel *less confident* that I'd pull off following [docs/developers/python](https://arrow.apache.org/docs/developers/python.html) without issue - as someone with less experience on projects with a compile-step. (*although #36411 may shake things up here*) GitHub link: https://github.com/apache/arrow/discussions/45919#discussioncomment-14574396 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
