Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Eli Zaretskii <eliz@gnu.org>, Tom Tromey <tom@tromey.com>
Cc: tdevries@suse.de, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/python] Use PyConfig for python 3.9
Date: Mon, 3 Nov 2025 12:09:05 -0500	[thread overview]
Message-ID: <a76c5e84-6bbe-4db7-82bc-c31140f7f6be@simark.ca> (raw)
In-Reply-To: <86v7jujkyh.fsf@gnu.org>

On 11/1/25 3:00 AM, Eli Zaretskii wrote:
>> From: Tom Tromey <tom@tromey.com>
>> Cc: Tom Tromey <tom@tromey.com>,  tdevries@suse.de,  gdb-patches@sourceware.org
>> Date: Fri, 31 Oct 2025 12:15:51 -0600
>>
>>>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>>
>> Eli> As long as the maintenance burden is not too heavy, I think we
>> Eli> shouldn't drop support of old versions.  It would be strange (for lack
>> Eli> of a better, but still polite, word) to drop support of XP just
>> Eli> because Python did.
>>
>> It's not just Python though.  Microsoft also dropped support for it 10
>> years ago.  So we're talking about holding back GNU development for the
>> sake of an obsolete proprietary system.
>>
>> I think it would be fine to declare GDB 17 as the last release that
>> supports XP.  Users who care about this -- and there cannot be many --
>> can just use that version in perpetuity.
> 
> We can discuss the broader issue of whether we want to drop support
> for XP, yes.  When we do, please explain how supporting it holds back
> GNU development, as the basis for the discussion, and let's take it
> from there.

One possibility is to declare that it's no longer possible to compile
GDB with Python support, on Windows XP, because we want to make use of
Python features newer that the latest Python that works on XP.

Simon

  reply	other threads:[~2025-11-03 17:09 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 [this message]
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)
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=a76c5e84-6bbe-4db7-82bc-c31140f7f6be@simark.ca \
    --to=simark@simark.ca \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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