Please, don't jump to stub files!

[cangyin]

For python 3.8.10, with pylance v2023.1.10

#!/usr/bin/python3

import sys

from unicodedata import category

Ctrl+Click on unicodedata jumps to the damn stub file, that's frustrating and drives me crazy.

Issues I read:

• Goto definition goes to stub files instead of actual definitions #65
• Go To Definition jumps to source rather than typeshed stubs pyright#795
• Go to definition goes to stub files instead of actual definitions #3227

But none of them actually solves the problem.

What in the end is the meaning for creating such stub files? Python is not C/C++, it does not need a header file!

[erictraut]

Where would you expect it to take you in this case? There is no unicodedata.py file. This module is implemented in C and compiled as part of the Python interpreter. That means there is no source code on your system that can be displayed. Pylance is falling back to the type stubs in this case because they at least provide you with the interface definitions for this module.

[cangyin]

Well, that sounds completely reasonable to me. But I suggest adding a heading comment for such stub files, telling for why the stub file is chosen to shown up.

So there will be less persons be confused by pylance not carrying them to the actual .py files.

[cangyin]

Thanks.