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

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

On Fri, Apr 7, 2023 at 12:23 PM João Távora <joaotavora@gmail.com> wrote:
>
> On Fri, Apr 7, 2023 at 12:17 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> >
> > Well, how about coding the test Michael asked, and I seconded, then?
> > I agree that it will be a much better use of our time than keeping
> > arguing about it.
> >
> > TIA
>
> Quoting myself:
>
> > > Show me the code that does that "checking if up to the job" and show
> > > me that it doesn't slow down Eglot tests significantly and I will
> > > consider it.   I don't have Debian to test. It's not a trivial job
> > >(at least I think so).  If it is trivial, then please help me.
>
> > > I think it's a much better effort spent to convert those tests from
> > > pylsp to clangd by the way.  So if you're goint to help me, you
> > > could start with that.  Probably easier too.
>
> Many TIAs

Alternatively, if helping me with that check or adding pip install
or not installing debian's pylsp on EMBA is too much to ask, then
just delete all the pylsp tests.

They've been there for a number of months now, and no reports
of this "real problem" you describe have ever surfaced.  And they
have existed in Eglot for a number of years, and also 0.0 reports.

João