Jedi searches the python interpreter in the wrong path. about jedi HOT 8 OPEN

This is searching bin/python in the virtual environment that was probably specified here. I'm pretty sure there is some misconfiguration here where a project exists that points towards a now defunct venv.

from jedi.

i never created a venv, neither i have a defunct one in the directory im modifying things in

from jedi.

The problem is that I have no way to debug this. This is not a pure Jedi call. I don't know what project is at this point. I have no idea about your system about installed Python version. So unless you start trying to debug this yourself (the environment.py code is extremely simple), I'm afraid I cannot help you.

I would be surprised if this was a fundamental issue. Jedi has been downloaded about 800 million times and it's used widely. This code hasn't changed a lot in a few years. So either it's a really strange edge case or something in your system is just broken.

from jedi.

same issue happening since 3 days ago

from jedi.

I found a simple fix: nuke $HOME/.cache/jedi, so i assume the problem is somehow related to cache

from jedi.

In jedilsp/jedi/api/project.py line 244 where it says:

if self._environment_path is not None:

it should instead read:

if self._environment_path:

…because this setting can also be the empty string when left unconfigured.

from jedi.

@wsldankers No. An empty path should behave like an empty path. I'm not sure what exactly happens in that case. If an empty string never provides any useful result we should let the user know that and raise an exception instead of just swallowing a very and invalid value. If it implies the "current working directory"? that might be a fine behavior.

from jedi.

Well if that's the case, how do I change it from an empty string to None? I have no idea.
Edit: that's probably IDE dependent. I'll need to look into that first.
Edit 2: this MAY be fixed in microsoft/vscode-python#22713 but that fix is not in a release yet.

In my case it's the vscode plugin that is sending an empty string as environmentPath over jsonrpc. If that is incorrect behavior it's not a bug in jedi. If this is the same issue that @Sniper10754 is experiencing, then this bug can probably be closed.

from jedi.