From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eric Blake <eblake@redhat.com>,
Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Cleber Rosa <crosa@redhat.com>
Cc: kwolf@redhat.com, den@openvz.org, vsementsov@virtuozzo.com,
Eduardo Habkost <ehabkost@redhat.com>,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] iotests: handle TypeError for Python3 in test 242
Date: Mon, 18 Feb 2019 22:25:12 +0100 [thread overview]
Message-ID: <4f992059-b448-a234-d319-3eb3bb5e04c9@redhat.com> (raw)
In-Reply-To: <2cbb158f-a869-e24c-96cc-23f7f61a946b@redhat.com>
On 2/18/19 9:05 PM, Eric Blake wrote:
> [adding Eduardo for some python 2-vs-3 advice]
And Cleber.
>
> On 2/18/19 1:59 PM, Andrey Shinkevich wrote:
>> To write one byte to disk, Python2 may use 'chr' type.
>> In Python3, conversion to 'byte' type is required.
>>
>> Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
>> ---
>> tests/qemu-iotests/242 | 9 +++++++--
>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/tests/qemu-iotests/242 b/tests/qemu-iotests/242
>> index 16c65ed..6b1f7b8 100755
>> --- a/tests/qemu-iotests/242
>> +++ b/tests/qemu-iotests/242
>> @@ -65,9 +65,14 @@ def toggle_flag(offset):
>> with open(disk, "r+b") as f:
>> f.seek(offset, 0)
>> c = f.read(1)
>> - toggled = chr(ord(c) ^ bitmap_flag_unknown)
>> + toggled = ord(c) ^ bitmap_flag_unknown
>> f.seek(-1, 1)
>> - f.write(toggled)
>> + try:
>> + # python2
>> + f.write(chr(toggled))
>> + except TypeError:
>> + # python3
>> + f.write(bytes([toggled]))
>
> Looks like it works, but I'm not enough of a python expert to know if
> there is a more Pythonic elegant approach.
>
> If someone else picks it up before my next NBD pull request,
> Acked-by: Eric Blake <eblake@redhat.com>
>
next prev parent reply other threads:[~2019-02-18 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 19:59 [Qemu-devel] [PATCH] iotests: handle TypeError for Python3 in test 242 Andrey Shinkevich
2019-02-18 20:05 ` Eric Blake
2019-02-18 21:25 ` Philippe Mathieu-Daudé [this message]
2019-02-22 0:17 ` Cleber Rosa
2019-02-22 9:48 ` Andrey Shinkevich
2019-02-19 10:30 ` Vladimir Sementsov-Ogievskiy
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=4f992059-b448-a234-d319-3eb3bb5e04c9@redhat.com \
--to=philmd@redhat.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=crosa@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).