Some issues on remote interpreter

[llan-ml]

Expected Behaviour

The remote interpreter works normally in the latest anaconda.

Actual Behaviour

As reported in https://github.com/DamnWidget/anaconda/issues/872#issuecomment-714366984

@scuml @DamnWidget After some trials, I found that the remote interpreter works well with 3fb82d6d253a617f83d82e010cc1e04fe93b13c5, and the problem seems to be introduced by 5af45c2e489621196a39ea8f82b154f8e6128193.

In addition, I found that, even with 3fb82d6d253a617f83d82e010cc1e04fe93b13c5, the remote interpreter cannot recognize paths for customized python modules; I tried passing the option -e path to minserver.py and setting the environment variable PYTHONPATH. This problem should be related to https://github.com/davidhalter/jedi/pull/1633, and we may need to update jedi to a newer version.

FYI @nicolas-renard

[diazcal]

Hey @llan-ml thanks for the commit hint! I am having some problems with the remote interpreter as well. I can confirm minserver.py works with 3fb82d6d253a617f83d82e010cc1e04fe93b13c5 and Jedi version 0.17.1

To solve the python modules situation minserver.py needs to be called with its absolute path (or at least this is how I solved my user modules problems). Not sure if that is the intended use or is supposed to work also from its relative path.

[llan-ml]

Hi @Neuchatel , the Jedi project automatically recognizes the modules in the current working directory. Thus, if we run python abspath_of_minserver.py after cd project_path, the Jedi can autocomplete the modules in our custom project.

One limitation is that we can only have one custom module path (i.e., the current working directory), though I think this can meet most of our needs.

[diazcal]

Yesterday I did some debugging trying to find out where the problem could be but nothing so far. Since I work under Linux I ended up creating symlinks of all my personal modules and linked them under my ~/.local/lib/python3.6/site-packages to have the autocompletion working while the issue is fixed.