Erik De Bonte

> [info] TypeError: e.clear is not a function This is a dupe of https://github.com/microsoft/pylance-release/issues/5000, which has been fixed in our prerelease builds.

Ok, I'll see if I can reproduce this. Could you provide a complete log file? Also, is your code publicly available somewhere?

> I assume it’s just a log file of the Python Language Server from VS Code startup to final crash of Pylance? Yes, please.

> I just received a Pylance crash just now. @holyoaks, that looks like https://github.com/microsoft/pylance-release/issues/5301. So far we've been unable to reproduce that issue. If you're able to reproduce it and...

Closing as both issues reported by the user are dupes -- #5000 (which has been fixed) and #5301 (which was closed due to lack of info). @holyoaks, if you are...

This issue has been fixed in prerelease version 2024.4.101, which we've just released. You can find the changelog here: [CHANGELOG.md](https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#20244101-10-April-2024-PreRelease)

It works properly if the files are in the root of the workspace rather than in `src`. The problem is that the `moduleName` value used by `SourceFile._buildFileInfo` is supplied when...

I was able to repro this on Linux and Windows. It won't repro until you launch VS Code from the project directory with the `python_env` activated. After that, you can...

The core problem here is that the `str` type is implemented in native code. We get the signature of `str.split` from typeshed's stdlib stubs, which are bundled with Pylance, but...

> Does pylance do something similar, dynamically generating docstrings? Or is actually more of a build-step kind of deal? Currently it happens dynamically by running the interpreter. I'm not sure...