From: Aaron Conole <aconole@redhat.com>
To: Adrian Moreno <amorenoz@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org (open list),
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
dev@openvswitch.org (open list:OPENVSWITCH),
linux-kselftest@vger.kernel.org (open list:KERNEL SELFTEST
FRAMEWORK), Pravin B Shelar <pshelar@ovn.org>,
"David S. Miller" <davem@davemloft.net>,
Shuah Khan <shuah@kernel.org>, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next] selftests: openvswitch: Fix escape chars in regexp.
Date: Wed, 17 Apr 2024 10:52:49 -0400 [thread overview]
Message-ID: <f7t7cgwavni.fsf@redhat.com> (raw)
In-Reply-To: <20240416090913.2028475-1-amorenoz@redhat.com> (Adrian Moreno's message of "Tue, 16 Apr 2024 11:09:13 +0200")
Adrian Moreno <amorenoz@redhat.com> writes:
> Character sequences starting with `\` are interpreted by python as
> escaped Unicode characters. However, they have other meaning in
> regular expressions (e.g: "\d").
>
> It seems Python >= 3.12 starts emitting a SyntaxWarning when these
> escaped sequences are not recognized as valid Unicode characters.
>
> An example of these warnings:
>
> tools/testing/selftests/net/openvswitch/ovs-dpctl.py:505:
> SyntaxWarning: invalid escape sequence '\d'
>
> Fix all the warnings by flagging literals as raw strings.
>
> Signed-off-by: Adrian Moreno <amorenoz@redhat.com>
> ---
Thanks, Adrian.
Reviewed-by: Aaron Conole <aconole@redhat.com>
next prev parent reply other threads:[~2024-04-17 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 9:09 [PATCH net-next] selftests: openvswitch: Fix escape chars in regexp Adrian Moreno
2024-04-17 14:52 ` Aaron Conole [this message]
2024-04-18 1:30 ` patchwork-bot+netdevbpf
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=f7t7cgwavni.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.org \
--cc=shuah@kernel.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