Stella

Could be the same issue as https://github.com/microsoft/pylance-release/issues/5524

Not sure what you mean by "more files to analyze". Can you share your log as described under "Filing an issue" in [the troubleshooting guide](https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue)? Thanks!

I see, the behavior you're seeing is related to https://github.com/microsoft/pylance-release/issues/5173. The `File to Analyze` count is actually the `Cells to Analyze` count. Simple `print` statements shouldn't cause pylance to fail...

Hi @vbem, if you don't want certain directories or paths to be included in the analysis, you can do the followings: 1. Open command palette, search for workspace settings. 2....

I debugged a little bit and found the wrong type is returned from https://github.com/microsoft/pyrx/blob/50b9544f921007da1d758ac69e61081987c6a65b/packages/pylance-internal/src/services/typeStringGenerator.ts#L60 I can take a closer look later. Also tagging @heejaechang

Looks like it only repros if the other symbol imported is the same type as the return type.

Does the bundled python version need to be updated for all past release branches? Or just the main?

The issue that tracks the general PTVS code changes:https://github.com/microsoft/PTVS/issues/7775

Hi @christopherdean11, thanks for exploring the feature! To try it out: 1. Place the cursor on the derived class name. 2. Wait for the light bulb icon to show up....

> My configuration of `python.analysis.diagnosticSeverityOverrides` is empty, both in user and workspace settings. There is no `# pyright` in all my code. Have you explicitly set the `reportUnknownVariableType` to `error`...