GitHub user dangotbanned added a comment to the discussion: A new home for pyarrow-stubs?
As a recent contributor and user of `pyarrow-stubs` (https://github.com/narwhals-dev/narwhals/issues/2124), this looks exciting! > We used `ty` and included a CI job that checks for annotation issues I feel the need to echo (https://github.com/apache/arrow/discussions/45919#discussioncomment-13496461) > both are designed to be much faster for large codebases, but neither is > production-ready. and again in (https://github.com/astral-sh/ty): > An extremely fast Python type checker and language server, written in Rust. > > Warning > > ty is in preview and is not ready for production use. > > We're working hard to make ty stable and feature-complete, but until then, > expect to encounter bugs, missing features, and fatal errors. I'm looking forward to using `ty` when it is ready, but there are major gaps in what is supported vs either [`pyright`](https://github.com/microsoft/pyright) or [`mypy`](https://github.com/python/mypy). There are two milestones that give a helpful overview of support: - [ ] [`ty` Beta](https://github.com/astral-sh/ty/milestone/2) - [ ] [`ty` GA](https://github.com/astral-sh/ty/milestone/4) Some select issues that seem relevant to `pyarrow-stubs` that I think *could* be a problem: - [ ] https://github.com/astral-sh/ty/issues/103 - [ ] https://github.com/astral-sh/ty/issues/117 - [ ] https://github.com/astral-sh/ty/issues/161 - [ ] https://github.com/astral-sh/ty/issues/544 - [ ] https://github.com/astral-sh/ty/issues/623 - [ ] https://github.com/astral-sh/ty/issues/868 - [ ] https://github.com/astral-sh/ty/issues/665 GitHub link: https://github.com/apache/arrow/discussions/45919#discussioncomment-13937459 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
