Bill Schnurr

How about providing some logs.. see https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue or any kind of similar notebook repo

the beginning would be more helps.. "Starting pylance"... etc with all the search paths and environment variables. or any special settings or paths your have

I see now there are return type hints. https://github.com/microsoft/LightGBM/blob/d0dfceec377d34cddd6722f870d073f7aa64ca2d/python-package/lightgbm/basic.py#L2755 I added stubs to address an issue with slow return type inference for function `self.get_data` in module `lightgbm.basic` logs: ``` (39760)...

I'll remove the bundled stubs when the next version of lightGBM, with type annotations, is released.

my stubs where generated using pylance/pyright by adding `# pyright: reportMissingTypeStubs=true` https://microsoft.github.io/pyright/#/type-stubs?id=generating-type-stubs

you can also use pyright to verify your type completeness of your public api (--verifytypes ). https://microsoft.github.io/pyright/#/command-line?id=pyright-command-line-options

@WyattGosling do you see this in your "Python Language Server" output window logs? `Enumeration of workspace source files is taking longer than 10 seconds` see https://github.com/microsoft/pylance-release/issues/3300#issuecomment-1406947296

are you using "openFileOnly" mode `"python.analysis.diagnosticMode": "openFilesOnly",` also see this issue on how to exclude folders https://github.com/microsoft/pylance-release/issues/4006#issuecomment-1443559636

Closing, sounds like exclude is working

We are updating the inlay hint insert to insert the needed imports as well. I'm not sure if VSCode has a general setting to disable inlay hint inserting, but i'm...