Exclude Jupyter notebooks completely from pyright

[medihack]

In my Django project I use some Jupyter notebooks in a separate notebooks folder. I want to completely exclude those notebooks from being scanned by pyright. That is why I tried the following setting in my pyproject.toml:

[tool.pyright]
exclude = ["**/notebooks", "**/.ipynb*"]
ignore = ["**/migrations", "**/notebooks", "**/.ipynb*"]
typeCheckingMode = "basic"
reportUnnecessaryTypeIgnoreComment = true

Unfortunately, the VS Code extension (v1.1.349) does not respect this setting and still reports some reportUndefinedVariable errors (that are defined in some previous cells). How do I completely turn off pyright (VS Code extension) for specific folders or files?

[erictraut]

Perhaps someone from the pylance team can answer this question. @debonte, @rchiodo?

[medihack]

I am not sure if it matters, but I am using the Pyright extension instead of Pylance. The last time I tried Pylance, it was far behind in the pyright version it integrates. So I switched to the Pyright extension, which always seems up-to-date.

[erictraut]

Pyright doesn't really have support for notebooks. That's something Pylance adds on top of pyright. The pylance team added some basic hooks for notebooks within the pyright code base, which is why I'm asking them for input.

I think the reason that "exclude" is not working here is because notebooks are not modeled as files. Each cell in a notebook is treated as a separate "document" from the perspective of the language server.

If support for notebooks is minimal (or broken) in pyright, we should probably just disable the support so it doesn't generate false positive errors.

[medihack]

I read that somewhere, too. That's why I tried to also exclude the whole notebooks folder. I also read somewhere that excluding **/.pynb* (instead of just **/.pynb) should help. Unfortunately, it doesn't. Pylance is not an option for us as some of my team members prefer Gitpod (where Pylance is not available) and (as mentioned) the internal pyright version is not really up-to-date.
Maybe disabling this feature in the Pyright extension is the best option then as it is not really helpful as it is right now.

[debonte]

I'm happy to look at this, but it'll probably need to wait until after the weekend.

[debonte]

This is a regression introduced by our recent URI refactoring. I opened #7215 to track it. See the issue for more details.