Problems with remote interpreter

Completed
Avatar
Permanently deleted user
Created

I am running into a problem with my remote interpreter, running on Vagrant. I am seeing the following error in my console:

Couldn't refresh skeletons for remote interpreter
failed to run generator3.py for vagrant:///Users/myuser/Work/gtt-web/var/www/myproject/env/bin/python, exit code 2, stderr:
-----
/var/www/myproject/env/bin/python: can't open file '/home/vagrant/.pycharm_helpers/generator3.py': [Errno 2] No such file or directory
-----

In my project settings, the remote interpreter shows fine, and it properly lists all the installed packages. I can also run my django dev server remotely as well. The problems happen when I try to run a manage.py task though, it gives me errors. Any suggestions what might be going on here?

This started when I rebuilt the vagrant instance with a newer version of the OS.

Votes

0

Share

3 comments
Avatar
t-moon
Created

I have the same problem:

I'm using:

* PyCharm 2017.3.4 Professional

* Docker

* Ubuntu 16.04 LTS

After configuration remote interpreter through the SSH I got an error in the pop-up:

failed to run generator3.py for ssh://root@127.0.0.1:2227/usr/bin/python3, exit code 2, 
stderr: ----- /usr/bin/python3: can't open file '/root/.pycharm_helpers/generator3.py': [Errno 2] No such file or directory -----

 

When I try to run remote debug I got:

ssh://root@127.0.0.1:2227/usr/bin/python3 -u /root/.pycharm_helpers/pydev/pydevd.py --multiproc --qt-support=auto --client '0.0.0.0' --port 33851 --file /app/manage.py runserver 0.0.0.0:8890
/usr/bin/python3: can't open file '/root/.pycharm_helpers/pydev/pydevd.py': [Errno 2] No such file or directory

Process finished with exit code 2

 

0
Avatar
t-moon
Created

It looks like I had a problem with tar.

Solution from here https://youtrack.jetbrains.com/issue/PY-27297#comment=27-2579940 helped me.

0
Avatar
Permanently deleted user
Created

Thanks for sharing that, it worked for me too. Interestingly, I am not using Linux on my system, I am using FreeBSD which uses BSD tar instead of GNU tar, but exhibits the same behaviour. I had to manually extract the archive, but everything works now as expected.

0

Please sign in to leave a comment.