Repository navigation
Language server unable to lint or analyze any classes imported by the pyarrow.lib commands, in the __init__.py #41736
Description
Describe the bug, including details regarding any error messages, version, and platform.
When using pyarrow classes Table, CompressedInputStream, BufferReader, and json, i can run the code, but for some reason my language server (and I've tried jedi, and pylance) cannot find/lint/or analyze any of these function or classes, or really anything imported by the pyarrow.lib , in the __init__.py file for the pyarrow directory. Is this expected?
Component(s)
Python
Activity
AntBlo commentedon Jun 6, 2024
According to a developer over at LanceDB, imported Cython code doesn't have type hints. So I think this is expected.
If there are any ongoing efforts to add type hints to pyarrow.lib though, I'd like to subscribe to it and perhaps help out if possible.
RanFeldesh commentedon Jun 27, 2025
This issue is getting more severe and relevant these days for VSCode users, since LLM agents are using the language server warnings output to automatically review the code they write and iterate on it (e.g. Claude Sonnet 4).
So the LLM agent writes a proper
pyarrow computecode, but then gets a pylance warning, and automatically starts to iterate on addressing it, degrading the original solution, many times ending in an infinite loop, or a non-functioning code, even though the first solution was fine.The impact is that this might move junior engineers away from pyarrow, choosing alternatives instead, and it lowers the productivity of essentially anyone.
Example: While
pc.multiplyis a valid method, pylance generates a warning, which is caught by the agent, who starts to make unnecessary changes:AntBlo commentedon Jul 9, 2025
Just a heads-up, I did find out there are stubs for pyarrow, but I don't think they're official or anything, so be careful as always depending on things: https://github.com/zen-xu/pyarrow-stubs
thisisnic commentedon Oct 22, 2026
@AlenkaF I'm going through old
Type: bugissues. This is the language server not resolving anything exported from the Cythonpyarrow.lib, which is the missing-type-stubs problem tracked in #32609, and there is no separate work to do here. OK to close as a duplicate of #32609?AlenkaF commentedon Oct 22, 2026
Yes, I think this issue can be closed and the progress of type hints work tracked in #32609.