public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/29287] New: PySys_SetPath has been deprecated in Python 3.11
Date: Sat, 25 Jun 2022 18:47:05 +0000 [thread overview]
Message-ID: <bug-29287-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29287
Bug ID: 29287
Summary: PySys_SetPath has been deprecated in Python 3.11
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: python
Assignee: unassigned at sourceware dot org
Reporter: mark at klomp dot org
Target Milestone: ---
The fedrawhide builder found an issue building against python 3.11:
https://builder.sourceware.org/buildbot/#/builders/84/builds/70
In file included from varobj.c:38:
python/python-internal.h: In function ‘void gdb_PySys_SetPath(const wchar_t*)’:
python/python-internal.h:189:17: error: ‘void PySys_SetPath(const wchar_t*)’ is
deprecated [-Werror=deprecated-declarations]
189 | PySys_SetPath (const_cast<GDB_PYSYS_SETPATH_CHAR *> (path));
| ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/python3.11/Python.h:96,
from python/python-internal.h:86:
/usr/include/python3.11/sysmodule.h:15:38: note: declared here
15 | Py_DEPRECATED(3.11) PyAPI_FUNC(void) PySys_SetPath(const wchar_t *);
| ^~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
make[2]: *** [Makefile:1896: varobj.o] Error 1
See https://docs.python.org/3.11/c-api/sys.html#c.PySys_SetPath
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-06-25 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 18:47 mark at klomp dot org [this message]
2022-06-28 17:33 ` [Bug python/29287] " tromey at sourceware dot org
2022-07-01 8:16 ` mark at klomp dot org
2023-03-17 18:34 ` tromey at sourceware dot org
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=bug-29287-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).