From: <Paul_Koning@Dell.com>
To: <doko@ubuntu.com>
Cc: <gdb@sourceware.org>, <libstdc++@gcc.gnu.org>, <dmalcolm@redhat.com>
Subject: Re: gdb pretty printers and python3.x
Date: Wed, 12 Jun 2013 14:59:00 -0000 [thread overview]
Message-ID: <C75A84166056C94F84D238A44AF9F6AD0341F889@AUSX10MPC102.AMER.DELL.COM> (raw)
In-Reply-To: <51B8394A.9040407@ubuntu.com>
On Jun 12, 2013, at 5:03 AM, Matthias Klose wrote:
> Starting with gdb-7.6, gdb supports embedding a Python3 interpreter instead of
> Python2. However most pretty printers are still using Python2 code, and when
> shipping a gdb using Python3, you have to fix all pretty printers at once (and
> keep building it with Python2, nobody will port to Python3). So some questions:
>
> - Is there a list of known pretty printers? So far I know about
> libstdc++, python, gtk, libreoffice.
>
> - Is there a minimal python version supported by gdb? If e.g. it is 2.6,
> then probably most pretty printers could be converted to code which can
> be used by both 2.x and 3.x. If not, then it would be up to 2to3 runs
> to do the conversion when needed.
The documented minimum is 2.4, I believe.
It's not hard to write code that works both with 2.4 and above, and with 3.x. The python code that's included with gdb is done that way, including the python section of the test suite. About the only areas that are a hassle are byte strings (since b"foo" is a syntax error in V2.x) and except clauses that use "except MyException as e". That second one was discussed on this list yesterday, the answer is simple, it's just not all that elegant.
paul
next prev parent reply other threads:[~2013-06-12 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 9:03 Matthias Klose
2013-06-12 14:59 ` Paul_Koning [this message]
2013-06-12 15:23 ` David Malcolm
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=C75A84166056C94F84D238A44AF9F6AD0341F889@AUSX10MPC102.AMER.DELL.COM \
--to=paul_koning@dell.com \
--cc=dmalcolm@redhat.com \
--cc=doko@ubuntu.com \
--cc=gdb@sourceware.org \
--cc=libstdc++@gcc.gnu.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