From: "Richard Earnshaw (foss)" <Richard.Earnshaw@arm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: simark@simark.ca, tom@tromey.com, tdevries@suse.de,
gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/python] Use PyConfig for python 3.9
Date: Wed, 12 Nov 2025 17:53:17 +0000 [thread overview]
Message-ID: <cdbd3988-3ab5-4c08-926c-7764ad7c7da0@arm.com> (raw)
In-Reply-To: <86seejrwpg.fsf@gnu.org>
On 12/11/2025 17:23, Eli Zaretskii wrote:
>> Date: Wed, 12 Nov 2025 16:52:13 +0000
>> Cc: tom@tromey.com, tdevries@suse.de, gdb-patches@sourceware.org
>> From: "Richard Earnshaw (foss)" <Richard.Earnshaw@arm.com>
>>
>>> Btw, the problem is not the system where GDB is compiled, the problem
>>> is the system on which it runs.
>>
>> So how long are we expected to support such an antiquated system?
>
> I think that depends on what is required to "support" them. That's
> what we should talk about, and in practical terms. E.g., if all
> that's required is not to delete compatibility code (and I'm not
> saying that's all, I'm just giving an example), it is my opinion that
> the effort is negligible.
>
>> It's already 11 years beyond it's final maintenance update and continuing to pretend we can support it is clearly holding up development of gdb.
>
> But does it hold development? If it does, let's identify where it
> does and talk about that, and maybe we will then decide that the
> effort is too much.
>
Well if it hinders developments like:
- switching to the python limited API
- removing the need to test against multiple python run-times
- removing the need for users to install a specific version of python rather than reuse the version they already have installed
then yes it does.
>> If the runtime can't support critical improvements of gdb, then surely it's time to reconsider our priorities.
>
> Yes, "if". The issue, once again, is whether this "if" indeed
> materializes. That's what I suggest to discuss.
next prev parent reply other threads:[~2025-11-12 17:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 13:36 Tom de Vries
2025-10-17 14:13 ` Tom Tromey
2025-10-17 15:11 ` Eli Zaretskii
2025-10-17 16:33 ` Tom Tromey
2025-10-17 18:34 ` Eli Zaretskii
2025-10-31 18:15 ` Tom Tromey
2025-11-01 7:00 ` Eli Zaretskii
2025-11-03 17:09 ` Simon Marchi
2025-11-03 18:21 ` Eli Zaretskii
2025-11-12 16:52 ` Richard Earnshaw (foss)
2025-11-12 17:23 ` Eli Zaretskii
2025-11-12 17:53 ` Richard Earnshaw (foss) [this message]
2025-11-12 18:03 ` Arsen Arsenović
2025-11-12 18:20 ` Eli Zaretskii
2025-11-12 19:24 ` Arsen Arsenović
2025-11-13 5:45 ` Eli Zaretskii
2025-10-17 16:51 ` Arsen Arsenović
2025-10-17 18:35 ` 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=cdbd3988-3ab5-4c08-926c-7764ad7c7da0@arm.com \
--to=richard.earnshaw@arm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tdevries@suse.de \
--cc=tom@tromey.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox