Open Jasha10 opened 2 years ago
Jedi does not respect MYPYPATH
, because it's fundamentally not mypy ;-)
Jedi follows this: https://peps.python.org/pep-0561/#type-checker-module-resolution-order
I guess just put stubs in front of code in the PYTHONPATH.
Jedi does not respect
MYPYPATH
, because it's fundamentally not mypy ;-)
Makes sense!
Jedi follows this: https://peps.python.org/pep-0561/#type-checker-module-resolution-order
I guess just put stubs in front of code in the PYTHONPATH.
Using PYTHONPATH=stubs:code
I am still getting jedi-vim: Couldn't find any definitions for this
when I call jedi#goto_stubs()
.
I'm keeping this open for now, but I feel like this might not be fixed, since currently nobody is actively working on Jedi.
I'm currently working on a Rust replacement for Jedi, but it will still take time (and it will probably support MYPYPATH).
Cool! I can't wait to see the new rust program.
I'm having trouble with discovery of
.pyi
stub files that live in a different folder from the.py
source file.Here is an example that works as expected:
If I set the environment variable
PYTHONPATH=code
and ifmain.py
contains the linefrom foo import bar
, thenjedi#goto_stubs()
works as expected (it finds the definition ofbar
incode/foo.pyi
).Here is an example that is not working:
I am having problems when the file layout looks like this:
In this situation,
jedi#goto_stubs()
does not work. I have tried the following environment variable settings:PYTHONPATH=code:stubs
PYTHONPATH=code MYPYPATH=stubs
I would expect that the
.pyi
file can be discovered as long as it is discoverable onPYTHONPATH
orMYPYPATH
, but this seems not to be the case.