GitHub user AlenkaF added a comment to the discussion: A new home for pyarrow-stubs?
Just wanted to keep this discussion active—following up with my thoughts on a possible path forward. I believe a good approach would be to coordinate efforts with the `pyarrow-stubs` project and build on the work that has already been done there. That said, I’m a bit uncertain, since @paleolimbot and @jorisvandenbossche have both expressed support for a simpler, auto-generated solution—and they’re usually right. 😊 That said, PyArrow developers are currently managing several priorities, so this likely isn’t something we can kick off immediately. Still, it would be valuable to start planning how we want to approach this. Based on the ongoing discussions, I’d like to highlight a couple of key points: - As Joris suggested, we could start with minimal, lightweight stubs—something simpler than what currently exists in `pyarrow-stubs`—and gradually extend them as needed ([comment](https://github.com/apache/arrow/issues/32609#issuecomment-2334113297)). - If transferring ownership of the `pyarrow-stubs` project would still be relevant, bringing it under the Apache Arrow umbrella would involve the official Apache donation process, starting with a vote on the mailing list. - It might also be worth creating a proof of concept for auto-generated stubs to compare approaches. Lastly, I was recently pointed to a new type checker tool: https://github.com/astral-sh/ty. Does anyone have experience with it? GitHub link: https://github.com/apache/arrow/discussions/45919#discussioncomment-13493054 ---- This is an automatically sent email for user@arrow.apache.org. To unsubscribe, please send an email to: user-unsubscr...@arrow.apache.org
