From: Romain GEISSLER <romain.geissler@amadeus.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: [committed] libstdc++: Reformat Python code
Date: Mon, 13 Nov 2023 15:29:38 +0000 [thread overview]
Message-ID: <D04538D8-E6DC-4D89-B7C3-E025081464BC@amadeus.com> (raw)
In-Reply-To: <CACb0b4=hEmrEKrO_9ZYddYKYEnYJ-hov6W8fYeoCTpP2OM9dxg@mail.gmail.com>
> Le 13 nov. 2023 à 16:24, Jonathan Wakely <jwakely@redhat.com> a écrit :
>
> Yes, I'll do that backport (and most of the other Python improvements
> too, at least for gcc-13).
>
> Thanks for raising it.
>
Cool thanks ! ;)
In the meantime, in my own toolchains I have silenced (without fixing it) the warnings
with this simple patch (in case anyone else wants to quickly get rid of it, but it’s not
really a good long term workaround).
--- libstdc++-v3/python/libstdcxx/v6/__init__.py
+++ libstdc++-v3/python/libstdcxx/v6/__init__.py
@@ -1 +1,2 @@
-
+import warnings
+warnings.filterwarnings("ignore", category=SyntaxWarning)
next prev parent reply other threads:[~2023-11-13 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230928202156.3004584-1-jwakely () redhat ! com>
2023-11-13 14:40 ` Romain GEISSLER
2023-11-13 15:24 ` Jonathan Wakely
2023-11-13 15:29 ` Romain GEISSLER [this message]
2023-09-28 20:21 Jonathan Wakely
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=D04538D8-E6DC-4D89-B7C3-E025081464BC@amadeus.com \
--to=romain.geissler@amadeus.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.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).