From: Joseph Myers <josmyers@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2] test_printers_common.py: Remove invalid escape sequence
Date: Mon, 12 Feb 2024 17:55:30 +0000 (UTC) [thread overview]
Message-ID: <cf3dc869-c564-40ed-ec4e-ec318c1d921@redhat.com> (raw)
In-Reply-To: <20240212140650.908586-1-hjl.tools@gmail.com>
On Mon, 12 Feb 2024, H.J. Lu wrote:
> - gdb_prompt = u'\(gdb\)'
> + gdb_prompt = u'\\(gdb\\)'
It's generally better to use r'' strings to avoid needing to double
backslashes. And u'' is obsolete in Python 3 (and our scripts don't
support Python 2 any more) so should not be used.
--
Joseph S. Myers
josmyers@redhat.com
prev parent reply other threads:[~2024-02-12 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 14:06 H.J. Lu
2024-02-12 14:14 ` Florian Weimer
2024-02-12 17:55 ` Joseph Myers [this message]
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=cf3dc869-c564-40ed-ec4e-ec318c1d921@redhat.com \
--to=josmyers@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).