Erik De Bonte

> Could we detect if this happens (e.g. there was an error with Pylance installation). > Or if we can not detect, should we just offer for existing Jedi users...

Seems like we should eliminate our `lxml` stubs and point people to https://github.com/lxml/lxml-stubs, or https://github.com/abelcheung/types-lxml may actually be preferred.

- Can you please provide a log as described under "Filing an issue" in [the troubleshooting guide](https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue)? - What version of Pylance do you have installed? - What is the...

@FMorschel, thanks for the issue. Can you please clarify what you are requesting here? The two VS Code screenshots look identical to me. In the PyCharm screenshots, it's not clear...

The TextMate scope for the escaped `{{` is correct -- `constant.character.escape.python`, which is the same as `\n`. The `{{` is shown with two colors because VS Code's `editor.bracketPairColorization.enabled` config setting...

@hediet, the problem here is that escaped bracket characters within Python f-strings are colored by VS Code's "bracket pair colorization" feature. Is this a VS Code bug, or is there...

> Can you try the "Inspect Tokens" command in VS Code and check if f-strings are marked as string? @hediet, here's what I see for the string text (ex. "Explicit...

> inlay hints is close, yes, but its a result of the type checking, not a input. @laundmo, as the tooltip in the screenshot indicates, you can double-click an inlay...

I believe that this is intentionally not supported for security reasons. We want users to opt into this feature explicitly to ensure that a malicious node.exe isn't used without their...

> `python.autoComplete.extraPaths` I hadn't heard of this setting before. FYI, it appears to only be honored when using Jedi instead of Pylance. https://github.com/microsoft/vscode-python/blob/01e5cbdbe836e51447a887f5afb350293a5ec11e/src/client/activation/jedi/analysisOptions.ts#L44