public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Samuel Bronson <naesten@gmail.com>
Cc: libstdc++@gcc.gnu.org, GCC Patches <gcc-patches@gcc.gnu.org>,
	       GDB Patches <gdb-patches@sourceware.org>,
	       Tom Tromey <tromey@redhat.com>,
	Matthias Klose <doko@ubuntu.com>
Subject: Re: [PATCH v3 3/3] Port libstdc++ pretty-printers to Python 2 + Python 3
Date: Fri, 11 Jul 2014 13:49:00 -0000	[thread overview]
Message-ID: <20140711134933.GB4871@redhat.com> (raw)
In-Reply-To: <8761j4imol.fsf@naesten.mooo.com>

On 10/07/14 22:48 -0400, Samuel Bronson wrote:
>	PR libstdc++/58962
>	* python/libstdcxx/v6/printers.py: Port to Python 2+3
>	  (imap): New compat function.
>	  (izip): Likewise.
>	  (Iterator): New mixin to allow writing iterators in Python 3 style
>	  regardless of which version we're running on.
>	  [Python3] (long) New compat alias for "int".
>	* testsuite/lib/gdb-test.exp: Port to Python 2+3 (print syntax)

Thanks, I've committed this with a few tiny changes to the comments
(s/compatability/compatibility/ and the comment about your GDB PR).

I'm not planning to backport this myself, but if the patch applies
cleanly or if someone else does the work then I have no objections to
it going on the release branches (after the branch reopens post-4.9.1
of course).

Thanks very much for doing this.

  reply	other threads:[~2014-07-11 13:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1400701554-18062-1-git-send-email-naesten@gmail.com>
2014-07-11  2:48 ` [PATCH v2 0/3] Port libstdc++ pretty printers to " Samuel Bronson
2014-07-11  2:49   ` [PATCH v2 1/3] Make libstdc++ testsuite work with pre-color GCC versions again Samuel Bronson
2014-07-11 15:33     ` Jonathan Wakely
2014-07-11  3:00   ` [PATCH v2 2/3] libstdc++ testsuite: Turn off GDB's auto-load, list loaded libs Samuel Bronson
2014-07-11 15:33     ` Jonathan Wakely
2014-07-11  3:22   ` [PATCH v2 3/3] Port libstdc++ pretty-printers to Python 2 + Python 3 Samuel Bronson
2014-07-11  3:45     ` [PATCH v3 " Samuel Bronson
2014-07-11 13:49       ` Jonathan Wakely [this message]
2014-07-21 17:06       ` Tom Tromey
2014-07-26  6:33         ` Samuel Bronson
2014-07-30 14:20           ` Tom Tromey

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=20140711134933.GB4871@redhat.com \
    --to=jwakely@redhat.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=naesten@gmail.com \
    --cc=tromey@redhat.com \
    /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).