public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: H.J. Lu <hjl@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] test_printers_common.py: Remove invalid escape sequence
Date: Mon, 12 Feb 2024 14:25:44 +0000 (GMT)	[thread overview]
Message-ID: <20240212142544.E7A3D3858401@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c676808a34e27fc3f7b1115c5257b382c6f00cb4

commit c676808a34e27fc3f7b1115c5257b382c6f00cb4
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Mon Feb 12 06:06:50 2024 -0800

    test_printers_common.py: Remove invalid escape sequence
    
    Change "\(" and "\)" to "\\(" and "\\)" in test_printers_common.py.  This
    fixes the test warning:
    
    .../scripts/test_printers_common.py:101: SyntaxWarning: invalid escape sequence '\('
    Reviewed-by: Florian Weimer <fweimer@redhat.com>

Diff:
---
 scripts/test_printers_common.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/test_printers_common.py b/scripts/test_printers_common.py
index bf700966ac..5c0d936fed 100644
--- a/scripts/test_printers_common.py
+++ b/scripts/test_printers_common.py
@@ -98,7 +98,7 @@ try:
     # If everything's ok, spawn the gdb process we'll use for testing.
     gdb = pexpect.spawn(gdb_invocation, echo=False, timeout=timeout,
                         encoding=encoding)
-    gdb_prompt = u'\(gdb\)'
+    gdb_prompt = u'\\(gdb\\)'
     gdb.expect(gdb_prompt)
 
 except pexpect.ExceptionPexpect as exception:

                 reply	other threads:[~2024-02-12 14:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240212142544.E7A3D3858401@sourceware.org \
    --to=hjl@sourceware.org \
    --cc=glibc-cvs@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).