question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

python language server not working

See original GitHub issue

Problem Description

No linting and pls just spins on the status line. I know this issue has been addressed in subsequent releases, but I am stuck with only being able to use packages from Anaconda’s main channel, which is woefully slow to update packages to newer versions.

If there were lines of code that needed to be altered or module(s) that needed to be updates, could you please point me to the link that might provide me with a solution so I can try to fix this manually (aka a backport fix would be appreciated).

Best regards

Versions

  • Spyder version: 5.1.5
  • Python version: 3.9.10
  • Qt version:
  • PyQt version:
  • Operating System name/version: Windows 11

Dependencies

Mandatory:

atomicwrites >=1.2.0 : 1.4.0 (OK) chardet >=2.0.0 : 4.0.0 (OK) cloudpickle >=0.5.0 : 2.0.0 (OK) cookiecutter >=1.6.0 : 1.7.3 (OK) diff_match_patch >=20181111 : 20200713 (OK) intervaltree >=3.0.2 : 3.1.0 (OK) IPython >=7.6.0 : 7.21.0 (OK) jedi >=0.17.2;<0.19.0 : 0.18.0 (OK) jsonschema >=3.2.0 : 3.2.0 (OK) keyring >=17.0.0 : 23.4.0 (OK) nbconvert >=4.0 : 5.6.1 (OK) numpydoc >=0.6.0 : 1.2 (OK) paramiko >=2.4.0 : 2.8.1 (OK) parso >=0.7.0;<0.9.0 : 0.8.3 (OK) pexpect >=4.4.0 : 4.8.0 (OK) pickleshare >=0.4 : 0.7.5 (OK) psutil >=5.3 : 5.8.0 (OK) pygments >=2.0 : 2.9.0 (OK) pylint >=2.5.0;<2.10.0 : 2.7.4 (OK) pyls_spyder >=0.4.0 : 0.4.0 (OK) pylsp >=1.2.2;<1.3.0 : 1.2.4 (OK) pylsp_black >=1.0.0 : None (OK) qdarkstyle =3.0.2 : 3.0.2 (OK) qstylizer >=0.1.10 : 0.1.10 (OK) qtawesome >=1.0.2 : 1.0.3 (OK) qtconsole >=5.1.0 : 5.3.0 (OK) qtpy >=1.5.0 : 2.0.1 (OK) rtree >=0.9.7 : 0.9.7 (OK) setuptools >=49.6.0 : 60.10.0 (OK) sphinx >=0.6.6 : 4.4.0 (OK) spyder_kernels >=2.1.1;<2.2.0 : 2.1.3 (OK) textdistance >=4.2.0 : 4.2.1 (OK) three_merge >=0.1.1 : 0.1.1 (OK) watchdog >=0.10.3 : 2.1.6 (OK) zmq >=17 : 22.2.1 (OK)

Optional:

cython >=0.21 : None (OK) matplotlib >=2.0.0 : 3.4.3 (OK) numpy >=1.7 : 1.20.1 (OK) pandas >=1.1.1 : 1.3.5 (OK) scipy >=0.17.0 : 1.6.2 (OK) sympy >=0.7.3 : 1.9 (OK)

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
Dan-Pattersoncommented, May 27, 2022

Many thanks to the two of you. I will give a few things a try… besides… who makes coding errors anyway 😉

0reactions
dalthvizcommented, May 27, 2022

I think from Spyder 5.1.5 to the current release 5.3.1 quite some work has been done related with the Python Language Server and not only over the Spyder side but also over the python-lsp-server (its current version is 1.4.1) and some plugins like pyls-black (its current version is 1.2.1).

Maybe you could try to edit the env where Spyder is intalled setting the minimum required versions for the python language server related packages as they were in the setup.py for Spyder 5.1.5: https://github.com/spyder-ide/spyder/blob/v5.1.5/setup.py#L203

Also, if it is possible for you to create a Spyder installation using Python 3.7.x that works without issue maybe doing a diff between the packages version installed with that Python version vs the versions installed when using Python 3.9 could give you some hints about what packages versions could help making the Python language server work.

If you can’t use the conda-forge channel or even pip (creating an env with only python from conda and then installing the rest using pip), I think there is not much that we can help, sorry 😕

About Anaconda, we don’t know either, actually some Spyder dependencies like QtConsole got updated on the default channel and that creates issues too since 5.1.5 is incompatible with recent version of those dependencies a no upper constraint was added so that ends up in issues related with incompatibilities 😕

Read more comments on GitHub >

github_iconTop Results From Across the Web

Python Language Server will not start when opening a file ...
OK, so the problem is not in intellicode. Try opening extension folder (Command palette - open extensions folder), locate mspython extension ...
Read more >
Settings Reference for Python - Visual Studio Code
The language server settings apply when python.languageServer is Pylance or Default . If you have difficulties with the language server, see Troubleshooting in ......
Read more >
Open Source VS Code Python Language Server Dies ...
Open Source VS Code Python Language Server Dies, Replaced by Proprietary Pylance ... Microsoft officially pounded the last nail into the open ...
Read more >
VSCode Python Language Server not shown anymore
Check your settings.json file to see if jedi is enabled ?
Read more >
python-language-server - PyPI
Installation. The base language server requires Jedi to provide Completions, Definitions, Hover, References, Signature Help, and Symbols: pip install python ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found