Eric Traut

Are you using VS Code with Pylance? I just tried opening your file `__init__.py` with the latest version of Pylance (2022.4.2) using VS Code, and code analysis and syntax highlighting...

This isn't a core type checking issue, so I'm going to transfer it to the pylance repo.

This happens because pyright doesn't see the file as a "*.ipynb". The file is being preprocessed (to combine all of the cells) in the notebook by the VS Code Python...

@debonte, is your theory that the parser is generating a range that includes the opening paren token but not the closed paren token? I could dig into that to confirm....

Thanks for reporting this. Yes, you're hitting a case that is difficult for the type analyzer to handle. I'll take a look at ways to mitigate the performance issue. Since...

I've done a series of performance improvements, and I've dropped the analysis time from 10's of seconds to about 2 seconds on my machine. This is definitely a challenging code...

I've marked it as "fixed in next version", but the optimizations are already in place, so I think it's fine to close this issue.

Ah, I see the problem. The expression `df1.col` is an unknown type because the `__getattr__` method on `NDFrame` doesn't have a return type annotation. ``` def __getattr__(self, name: _str) :...

The bug was reported against 2022.4.3, so I think we should reopen. However, we're going to need much more information to diagnose the problem — preferably a clear set of...

@pradyunsg, are you opening your volume root directory as a folder? When you open a folder within VS Code, Pylance assumes that your project is rooted in that directory and...