bug#62694: 30.0.50; eglot-tests fails with recent pylsp

[João Távora]

On Fri, Apr 7, 2023 at 8:44 AM Michael Albinus <michael.albinus@gmx.de> wrote:

> Don't know, I have no knowledge about language servers. But I would
> expect, that you first check whether pylsp is installed (you do it
> already), and then you could connect to pylsp, send a specific request,
> and decide, based on the ansewer, whether it is a proper language
> server.

Connect to a language server just to discover if I can run a test?

All to get around (presumably) faulty Debian packaging of
an obscure language server that almost noone uses when a perfectly
good alternative to install said obscure already exists?

> >> > Are you just trying to get the best possible coverage from 
> >> > eglot-tests.el?
> >> > Thanks, but then I'd focus on rust-analyzer first, or the Java jdtls 
> >> > server.
> >> > The latter would be really useful as the GitHub CI isn't currently
> >> > installing it and the test is being skipped there.
> >>
> >> If you could show me the Debian way to install rust-analyzer or jdtls in
> >> Debian, I'm your man. I didn't find a corresponding package (but
> >> honestly, I haven't tried for days). In case such packages don't exist
> >> yet for Debian, I would be willing to install them differently, for a 
> >> while.
> >
> > What is with this blind devotion to Debian?  It's a nice distro, but
> > surely it can handle installation of software in different ways.
>
> In this case, it is Emba indeed. We have decided to run our tests based
> on Debian. I don't see a reason to change this decision.

I'm not asking you to.  Debian is a fine distro, but it's not perfect.
Debian supports pip surely, so just install pylsp from pip.  Boom,
problem solved.