qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, "Kevin Wolf" <kwolf@redhat.com>,
	qemu-block@nongnu.org, "Juan Quintela" <quintela@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Max Reitz" <mreitz@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Cleber Rosa" <crosa@redhat.com>, "Fam Zheng" <famz@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [RFC 05/10] python: futurize -f lib2to3.fixes.fix_standarderror
Date: Mon, 14 May 2018 15:28:02 +0100	[thread overview]
Message-ID: <20180514142802.GL5182@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180511222052.8734-6-ehabkost@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

On Fri, May 11, 2018 at 07:20:47PM -0300, Eduardo Habkost wrote:
> Rename StandardError to Exception.
> 
> This is necessary for Python 3 compatibility.
> 
> Done using:
> 
>   $ py=$( (g grep -l -E '^#!.*python';find -name '*.py' -printf '%P\n';) | \
>     sort -u | grep -v README.sh4)
>   $ futurize -w -f lib2to3.fixes.fix_standarderror $py
> 
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
>  scripts/qmp/qemu-ga-client | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2018-05-14 14:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 22:20 [Qemu-devel] [RFC 00/10] [TESTING NEEDED] python: futurize --stage1 (Python 3 compatibility) Eduardo Habkost
2018-05-11 22:20 ` [Qemu-devel] [RFC 01/10] python: futurize -f libfuturize.fixes.fix_print_with_import Eduardo Habkost
2018-05-14 14:20   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-05-11 22:20 ` [Qemu-devel] [RFC 02/10] python: futurize -f libfuturize.fixes.fix_absolute_import Eduardo Habkost
2018-05-14 14:25   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-05-11 22:20 ` [Qemu-devel] [RFC 03/10] python: futurize -f libfuturize.fixes.fix_next_call Eduardo Habkost
2018-05-14 14:26   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-05-11 22:20 ` [Qemu-devel] [RFC 04/10] python: futurize -f lib2to3.fixes.fix_has_key Eduardo Habkost
2018-05-14 14:27   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-05-14 15:35   ` [Qemu-devel] " Philippe Mathieu-Daudé
2018-05-11 22:20 ` [Qemu-devel] [RFC 05/10] python: futurize -f lib2to3.fixes.fix_standarderror Eduardo Habkost
2018-05-14 14:28   ` Stefan Hajnoczi [this message]
2018-05-11 22:20 ` [Qemu-devel] [RFC 06/10] python: futurize -f lib2to3.fixes.fix_reduce Eduardo Habkost
2018-05-14 14:28   ` Stefan Hajnoczi
2018-05-11 22:20 ` [Qemu-devel] [RFC 07/10] python: futurize -f lib2to3.fixes.fix_tuple_params Eduardo Habkost
2018-05-14 14:29   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-05-11 22:20 ` [Qemu-devel] [RFC 08/10] python: futurize -f lib2to3.fixes.fix_renames Eduardo Habkost
2018-05-14 14:30   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-05-11 22:20 ` [Qemu-devel] [RFC 09/10] python: futurize -f lib2to3.fixes.fix_except Eduardo Habkost
2018-05-14 14:30   ` Stefan Hajnoczi
2018-05-11 22:20 ` [Qemu-devel] [RFC 10/10] python: futurize -f lib2to3.fixes.fix_numliterals Eduardo Habkost
2018-05-14 14:30   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-05-14 15:35   ` [Qemu-devel] " Philippe Mathieu-Daudé
2018-05-11 22:34 ` [Qemu-devel] [RFC 00/10] [TESTING NEEDED] python: futurize --stage1 (Python 3 compatibility) no-reply
2018-05-14  8:50 ` Dr. David Alan Gilbert
2018-05-16 11:39 ` Max Reitz
2018-05-17  7:48 ` Fam Zheng

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=20180514142802.GL5182@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=crosa@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@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 NNTP newsgroup(s).