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

["João Távora" <joaotavora@gmail.com>]

Michael Albinus <michael.albinus@gmx.de> writes:

> 	   (:name "pylsp" :version "1.4.1")))

This is not a version problem, Michael.  I have 1.7.2. running on my
laptop and it passes all the tests.  You say

> The initialization handshake is identical, except the server info

> I have absolutely no idea about the language server protocol, and
> whether both server replies are valid communication. If both are valid,
> eglot shall support this.

Then how, given the information that I've just given you (that pylsp
1.7.2 passes all the tests), do you plan to do to version checking??

We did version checking with clangd, that's reasonable, but here it
seems impossible.  Just go easy on the "shall"s and consider.

   pip install "python-lsp-server[all]"

you can even pin it to a specific version

   pip install "python-lsp-server[all]" pylsp=1.7.2

Thank you very much for using your Debian to check this, but you're
wasting your time.  Since you have "absolutely no idea about the LSP",
can't you "trust" me on this one?  LSP coordinates capabilities using
the handshake's capability statements.  You have witnessed an identical
capability statement and yet different behaviour.  The servers are _not_
perfect, and Debian's pylsp installation is subtly not behaving
correctly.

> If not, I believe eglot shall raise an error like "protocol mismatch",

This doesn't exist in LSP.  It just doesn't exist.  There are no
protocol versions.

> I have done the homework (not mine!)

The suggestion that you're doing my homework and I'm somehow
lazying about is not very amusing.

João