From: "João Távora" <joaotavora@gmail.com>
To: Basil Contovounesios <contovob@tcd.ie>
Cc: 62694@debbugs.gnu.org, Michael Albinus <michael.albinus@gmx.de>
Subject: bug#62694: 30.0.50; eglot-tests fails with recent pylsp
Date: Sun, 09 Apr 2023 15:45:22 +0100 [thread overview]
Message-ID: <87ttxpf725.fsf@gmail.com> (raw)
In-Reply-To: <874jppb388.fsf@tcd.ie> (Basil Contovounesios's message of "Sun, 09 Apr 2023 14:21:43 +0100")
Basil Contovounesios <contovob@tcd.ie> writes:
> The CI probably installs anew each time it runs, whereas I was hinting
> (sorry for not making it clearer) at the case where a local user updates
> pip packages over time.
Well, I'm a "local user" updating pip packages overtime, and used that
command and it worked (i used to to rev up pylsp to 1.7.2). Anyway, we
were talking EMBA anyway, which is a CI system installing it anew each time.
>> Who knows? Did you try it?
>
> I only tried the aforementioned patch at the time.
>
> I was just clarifying for posterity that the issue may well have lain
> with a component of pylsp rather than the version of the server itself,
> which is what this discussion focused on.
Sure, could be. Any number of things could have been it. I've just
forcibly uninstalled autopep8 here and I just got one failure, not all
that Michael reported. The one thing that could have solved it was
never even tried.
>> If it works i would have been happy to accept it Noone proposed
>> it. Instead, some truly vague and complex vapourware things were
>> proposed.
>
> That earlier proposals were not complete, optimal, or up to yours or
> anyone's standards does not warrant degrading them, IMO.
- vague: there are no details, just the idea of "checking if the server
is up to the job".
- complex: whatever its elusive nature is, probably more complex than
(skip-unless (executable-find "pylsp"))
- vapourware: 0 code
So no degradation or even standard-checking going on here. Primarily
because there was absolutely nothing brought forth to degrade or to
check standards on.
Also FTR, I wasn't the one who suggested I was doing other people's
homework.
> Like you, we're all here just trying to improve Emacs in whatever way
> we can.
Sure. I believe thanked Michael multiple already for taking an interest
in Eglot's tests. If I didn't, I do so again. And I thank you too, of
course. But it's certainly not "whatever way we can" if you obstinately
refuse to even try the one-liner suggestion of your interlocutor that
would probably fix the EMBA issue.
The academically postulated, never-demonstrated, "larger" issue of Emacs
developers running Eglot tests and facing non-determinism w.r.t to
external programs (why not w.r.t. cosmically induced bit-flipping, for
that matter?) probably cannot ever be fixed in this universe.
João
next prev parent reply other threads:[~2023-04-09 14:45 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 9:55 bug#62694: 30.0.50; eglot-tests fails with recent pylsp Michael Albinus
2023-04-06 10:54 ` João Távora
2023-04-06 11:22 ` Michael Albinus
2023-04-06 12:49 ` João Távora
2023-04-06 14:58 ` Michael Albinus
2023-04-06 16:59 ` João Távora
2023-04-06 17:39 ` Michael Albinus
2023-04-06 19:50 ` João Távora
2023-04-07 7:44 ` Michael Albinus
2023-04-07 10:20 ` João Távora
2023-04-07 10:29 ` Michael Albinus
2023-04-07 10:47 ` João Távora
2023-04-07 10:50 ` Michael Albinus
2023-04-07 10:57 ` João Távora
2023-04-07 11:04 ` Gregory Heytings
2023-04-07 11:10 ` João Távora
2023-04-07 11:11 ` Eli Zaretskii
2023-04-07 11:20 ` João Távora
2023-04-07 12:20 ` Michael Albinus
2023-04-07 10:43 ` Eli Zaretskii
2023-04-07 10:51 ` João Távora
2023-04-07 10:53 ` Michael Albinus
2023-04-07 10:59 ` Eli Zaretskii
2023-04-07 11:06 ` João Távora
2023-04-07 11:17 ` Eli Zaretskii
2023-04-07 11:23 ` João Távora
2023-04-07 11:37 ` João Távora
2023-04-07 11:41 ` Michael Albinus
2023-04-07 11:47 ` João Távora
2023-04-07 11:53 ` João Távora
2023-04-07 12:07 ` Eli Zaretskii
2023-04-07 12:13 ` Michael Albinus
2023-04-07 12:22 ` Eli Zaretskii
2023-04-07 12:40 ` João Távora
2023-04-07 12:58 ` Gregory Heytings
2023-04-07 13:02 ` João Távora
2023-04-07 13:57 ` Eli Zaretskii
2023-04-07 12:59 ` Michael Albinus
2023-04-07 13:48 ` Eli Zaretskii
2023-04-07 13:57 ` Michael Albinus
2023-04-07 14:00 ` Eli Zaretskii
2023-04-07 14:04 ` João Távora
2023-04-07 14:33 ` Eli Zaretskii
2023-04-07 15:06 ` Michael Albinus
2023-04-07 19:05 ` João Távora
2023-04-09 13:49 ` Michael Albinus
2023-04-07 12:04 ` Michael Albinus
2023-04-07 12:24 ` João Távora
2023-04-07 12:47 ` Michael Albinus
2023-04-07 13:01 ` João Távora
2023-04-07 13:04 ` Michael Albinus
2023-04-09 11:24 ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-09 11:22 ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-09 12:41 ` João Távora
2023-04-09 13:21 ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-09 14:45 ` João Távora [this message]
2023-04-09 15:32 ` Michael Albinus
2023-04-09 15:48 ` João Távora
2023-04-09 16:08 ` Michael Albinus
2023-04-09 18:17 ` João Távora
2023-04-09 19:04 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttxpf725.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=62694@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.