public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/29245] [gdb/testsuite, python2] FAIL: gdb.python/py-mi-cmd.exp: -pycmd bk3 (unexpected output)
Date: Sat, 11 Jun 2022 16:20:04 +0000	[thread overview]
Message-ID: <bug-29245-4717-uNohLeaVW9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29245-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29245

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Using a standalone reproducer:
...
$ cat test.py
class BadKey:
    def __repr__(self):
        return "Bad Key"


class ReallyBadKey:
    def __repr__(self):
        return BadKey()

a = {"result": {ReallyBadKey(): "world"}}

print (a)
...
we can see the behaviour with python3:
...
$ python3 test.py
Traceback (most recent call last):
  File "test.py", line 12, in <module>
    print (a)
TypeError: __repr__ returned non-string (type BadKey)
...
and python2:
...
$ python2 test.py
{'result': {Traceback (most recent call last):
  File "test.py", line 12, in <module>
    print (a)
TypeError: __repr__ returned non-string (type instance)
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2022-06-11 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 16:05 [Bug python/29245] New: " vries at gcc dot gnu.org
2022-06-11 16:20 ` vries at gcc dot gnu.org [this message]
2022-06-13 16:14 ` [Bug python/29245] " vries at gcc dot gnu.org

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=bug-29245-4717-uNohLeaVW9@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).