Goto definition goes to stub files instead of actual definitions

[kylebebak]

This makes code navigation in the standard library a lot less useful. In the standard library there are no inlined type annotations; there are type stubs for almost everything.

This means Jedi won't show you doc strings for most things in the standard library. It also makes code navigation in 3rd party libraries that use type stubs instead of inlined type annotations a lot less useful, for the same reason.

This is basically a duplicate of these pylance issues:

• Goto definition goes to stub files instead of actual definitions microsoft/pylance-release#65
• Goto definition goes to stub files instead of actual definitions microsoft/pylance-release#949

Would there be a way to have goto definition go to source code rather than type stubs, even if type stubs exist?

[davidhalter]

Which language server are you using?

The thing is: Jedi is flexible, have a look:

def goto(self, line=None, column=None, *, follow_imports=False, follow_builtin_imports=False,
         only_stubs=False, prefer_stubs=False):                             

Someone probably used prefer_stubs=True. This is probably an oversight on their end OR (more likely) you are are using the wrong LSP commands :) There's goto "definition" and goto "implementation", whereas the later should land in the standard library. BTW: There's also goto "typeDefinition", which is something else again.

This is basically a duplicate of these pylance issues:

No, those issues actually say the exact opposite thing.