From: Tom Tromey <tom@tromey.com>
To: Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org>
Cc: Kevin Buettner <kevinb@redhat.com>, Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH v2] Handle Python 3.11 deprecation of PySys_SetPath and Py_SetProgramName
Date: Fri, 15 Jul 2022 12:37:54 -0600 [thread overview]
Message-ID: <87k08enrwd.fsf@tromey.com> (raw)
In-Reply-To: <20220709155009.176955-1-kevinb@redhat.com> (Kevin Buettner via Gdb-patches's message of "Sat, 9 Jul 2022 08:50:10 -0700")
>>>>> "Kevin" == Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org> writes:
Kevin> Python 3.11 deprecates PySys_SetPath and Py_SetProgramName. The
Kevin> PyConfig API replaces these and other functions. This commit uses the
Kevin> PyConfig API to provide equivalent functionality while also preserving
Kevin> support for older versions of Python, i.e. those before Python 3.8.
[...]
This looks good to me. Thank you for doing this.
I think this fixes a couple of bugs in bugzilla, so those should be
mentioned in the commit message IMO.
Tom
next prev parent reply other threads:[~2022-07-15 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 15:50 Kevin Buettner
2022-07-15 18:37 ` Tom Tromey [this message]
2022-07-15 20:05 ` Kevin Buettner
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=87k08enrwd.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=simark@simark.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).