Unable to start the Python language server

[mzannoni]

Of course, pyls is correctly installed, Python and Python3 are present in /usr/bin.
From inside Python, I can import pyls without issue.
Until yesterday it was ok.

[lgeiger]

We just released v0.2.3 with a fix for properly recognizing pyls.
Could you try again with v0.2.3?

[mzannoni]

Nope... still the same.
I attach here a screenshot of the error in Atom.

Since it's started occurring it's always the same, and of course the Python IDE in Atom does not appear to work.

Let me know if you need more details about my system.

Other question... is there a way to install the latest version that was working correctly? I'd really need it...

[mzannoni]

If it can be of any help, output from Python interpreter:

...$ python3
Python 3.5.2 (default, Sep 14 2017, 22:51:06)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyls
>>> pyls.__version__
'0.8.0'
>>>

[mzannoni]

Ok, found an issue, I guess it's probably only in my case... Somehow the pyls bin was not in the PATH. Now it seems to work, after I've added it to the PATH in bash profile.
I think it was my mistake, I guess we can close this.

[lgeiger]

Glad it's working now. If you don't want to add pyls to your path in the bashrc, you can also configure the absolut path to pyls in the ide-python settings.

[mzannoni]

Thanks a lot. Still wondering what changed that broke it at a certain point... However, now it's ok. On Oct 29, 2017 11:17, "Lukas Geiger" <notifications@github.com> wrote: Glad it's working now. If you don't want to add pyls to your path in the bashrc, you can also configure the absolut path to pyls in the ide-python settings. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ab6thlRAg90YZcMyF4VsMhXm_K84JAACks5sxFCogaJpZM4QCGHb> .

[DreamAccess]

Hello everyone,

I am getting the same error, please can you tell me how you fixed your issue ?

Thank you.

[danielrocker]

in terminal:
atom --safe (do not load packages)

in atom:

file > quit

then start Atom again by the icon

Sorry about English

[LihengGong]

Same issue here:

python
Python 3.6.3 |Anaconda, Inc.| (default, Oct 27 2017, 12:14:30)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

>>> import pyls
>>> pyls.__version__
'0.19.0'
>>> exit()

---

Unable to start the Python language server.
Make sure to install pyls 0.19 or newer by running:

python -m pip install 'python-language-server[all]'
Install InstructionsDownload Python

[mzannoni]

In general, I could fix this issue in basically all of my machines (real, virtual, Fedora, Ubuntu, ...) with the following two commands in the terminal:
pip3 install --user --upgrade python-language-server[all]
pip install --user --upgrade python-language-server[all]

I don't know why, but upgrading pyls and its dependencies for both Python3 and Python2 fixes the issue for me in most cases.

It may be also useful, before the two commands above, to upgrade pip itself:
pip3 install --user --upgrade pip

[DavidMStraub]

In my case the problem was that pyls was only installed for Python 3, but the Python executable in the ide-python settings was set to the default value python (calling Python 2 on Ubuntu). Setting this to python3 solved the problem for me.

[shred86]

Thanks @DavidMStraub, setting the 'Python Executable' to python3 under Settings for ide-python fixed it for me.

[dstanner]

I was having this problem and none of the above solutions were working for me. pyls was working find when I'd start from the command line, but not when I'd start from the app icon.

But then I realized I had pip installed while in an anaconda virtualenv. I exited the virtualenv to my base environment, then pip installed again, and now it seems to be working fine.

So, if you're having this problem and installed from within the virtualenv, try re-installing in the base env.