From: Eli Zaretskii <eliz@gnu.org>
To: 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: Fri, 17 Oct 2025 21:34:17 +0300 [thread overview]
Message-ID: <86ikgdfkd2.fsf@gnu.org> (raw)
In-Reply-To: <87qzv1pjy8.fsf@tromey.com> (message from Tom Tromey on Fri, 17 Oct 2025 10:33:03 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>, tdevries@suse.de, gdb-patches@sourceware.org
> Date: Fri, 17 Oct 2025 10:33:03 -0600
>
> >> I wonder if anyone even uses that version. It has been EOL'd.
>
> Eli> We still support Python 3.4, because that's the only version available
> Eli> on Windows XP.
>
> Yeah, but does anyone use 3.8.
I don't know.
> As for XP, I tend to think the few remaining people on that system
> should just use an older gdb. They could use gdb 17 for example and we
> could move on.
As long as the maintenance burden is not too heavy, I think we
shouldn't drop support of old versions. It would be strange (for lack
of a better, but still polite, word) to drop support of XP just
because Python did.
next prev parent reply other threads:[~2025-10-17 18:38 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 [this message]
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)
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=86ikgdfkd2.fsf@gnu.org \
--to=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