Jake Bailey

I would consider trying out our new LS, [Pylance](https://devblogs.microsoft.com/python/announcing-pylance-fast-feature-rich-language-support-for-python-in-visual-studio-code/), to see if its performance characteristics work better for you.

This seems like an interplay between git's choice of line endings and the config, where it's checking it out as LF, not CRLF. We've typically worked on Windows in VS,...

You used the question template, the issue template asks for a lot more info. The trace logs would be important to look at, for the paths being used. https://github.com/microsoft/python-language-server/blob/master/TROUBLESHOOTING.md#filing-an-issue

Please, provide logs. The page I linked has the settings to enable trace logging and where to find it in VS Code.

I tried doing the above and running the test suite. All of our tests pass, except: ``` TypeShedSysExcInfo Source: TypeshedTests.cs line: 42 Duration: 11 sec Message: Expected Type.Name to be...

Since typeshed has started using `__` prefixes to indicate positional-only parameters (as the stub syntax is fixed to an older Python 3 syntax), we may need to consider some pre-processing...

Also, we'll need to add support (or at least declare) `Protocol`. For our sake, it should be sufficient to declare this as an empty class (since all subclasses of Protocol...

Marking as a 3.8, since there's going to be new stuff.

Current blockers to upgrade, strictly from the test front: - `GenericsTest.GenericPath` - Fails because `PurePath` as the bound to `_T` was changed from string form to a forward reference (not...

I think we're not going to be able to just upgrade typeshed without some major type system changes. Instead, we'll wait for 3.8 to be "done" upstream, then fork it...