Erik De Bonte

@erictraut is the best person to answer this, but I believe it is by design given our import resolution order described here: https://microsoft.github.io/pyright/#/import-resolution?id=resolution-order. Here are some ways you could fix...

> Note that it doesn't complain if I rename `typing_extensions.py` to `typing_extensions_1.py`. Yes, that's because when you import `typing_extensions` it's resolving to the `typing_extensions` in typeshed. When you give it...

> If it can't resolve the module, it should move on the step 6: Yes, but it did resolve the module. It found it in Pylance's bundled copy of typeshed....

Changing the shadowed import diagnostic behavior isn't going to change how the import is resolved though. Are you saying that one of the alternatives I listed above would work for...

> It's fine to resolve to the stub file, but isn't there a second kind of resolving going on: Yes, we do a separate resolution to look for the source...

The log above looks like the log from the Python extension. Assuming that you are using Pylance as your language server (that's the default), could you please provide the Pylance...

@umarbutler, can you provide a "Python Language Server" log from a case where Pylance crashed?

@GXY0116, can you provide the entire log? Drag it into the log as an attachment, assuming it's large.

> 2024-07-19 00:23:45.268 [info] [Info - 12:23:45 AM] (2577591) Heap stats: total_heap_size=289MB, used_heap_size=256MB, cross_worker_used_heap_size=256MB, total_physical_size=289MB, total_available_size=3882MB, heap_size_limit=4144MB > ... > 2024-07-19 00:24:15.581 [info] [Error - 12:24:15 AM] Server process exited...

@umarbutler we don't have any evidence yet that the two of you are hitting the same issue. Can you file a new issue and attach a log file? We can...