public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: jkratoch@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] tromey/python: py-value.exp: Fix Python3 incompatibilities. Date: Mon, 16 Feb 2015 14:41:00 -0000 [thread overview] Message-ID: <20150216144145.14861.qmail@sourceware.org> (raw) The branch, tromey/python has been updated via d1a09bf2f8e7e3f752a1bbeba135bc080bf0c865 (commit) from 89a19af106857845ac47c2e400f71631c36641e5 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit d1a09bf2f8e7e3f752a1bbeba135bc080bf0c865 Author: Jan Kratochvil <jan.kratochvil@redhat.com> Date: Mon Feb 16 15:41:28 2015 +0100 py-value.exp: Fix Python3 incompatibilities. ----------------------------------------------------------------------- Summary of changes: gdb/testsuite/gdb.python/py-value.exp | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) First 500 lines of diff: diff --git a/gdb/testsuite/gdb.python/py-value.exp b/gdb/testsuite/gdb.python/py-value.exp index 31b5910..58cce09 100644 --- a/gdb/testsuite/gdb.python/py-value.exp +++ b/gdb/testsuite/gdb.python/py-value.exp @@ -394,7 +394,7 @@ proc test_value_after_death {} { proc test_cast_regression {} { gdb_test "python v = gdb.Value(5)" "" "create value for cast test" gdb_test "python v = v.cast(v.type)" "" "cast value for cast test" - gdb_test "python print v" "5" "print value for cast test" + gdb_test "python print(v)" "5" "print value for cast test" } # Regression test for invalid subscript operations. The bug was that hooks/post-receive -- Repository for Project Archer.
reply other threads:[~2015-02-16 14:41 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=20150216144145.14861.qmail@sourceware.org \ --to=jkratoch@sourceware.org \ --cc=archer-commits@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: linkBe 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).