GitHub user yangdanny97 edited a comment on the discussion: A new home for pyarrow-stubs?
But also, I don't think the stubs work needs to be blocked on waiting for a particular typechecker to be ready - picking a typechecker isn't an irreversible decision and you could use existing tools like mypy and pyright to build a solution, then migrate later if another typechecker works better. It would be very nice for pyarrow-stubs to be integrated directly since it's fairly high quality as far as I can tell, but if it becomes unmaintained it will bit-rot and become stale very quickly. As a temporary measure I could add it to typeshed which would force it to be updated with each arrow release, but the typeshed maintainers are stretched extremely thin right now so I wouldn't want it to be a permanent solution. Once arrow gets stubs/inline types we could remove any typeshed stubs 6 months later. GitHub link: https://github.com/apache/arrow/discussions/45919#discussioncomment-13496719 ---- This is an automatically sent email for user@arrow.apache.org. To unsubscribe, please send an email to: user-unsubscr...@arrow.apache.org
