From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, ross@burtonini.com
Subject: Re: [Qemu-devel] Making QEMU build with Python 3
Date: Wed, 9 Aug 2017 14:10:32 +0100 [thread overview]
Message-ID: <20170809131032.GH24723@redhat.com> (raw)
In-Reply-To: <CAJSP0QVrCm6TfgU0dsXbudaW3gmGo0YQTTWbNypx6st6mKcSKA@mail.gmail.com>
On Wed, Aug 09, 2017 at 11:16:58AM +0100, Stefan Hajnoczi wrote:
> Ross created a bug to track Python 3 support:
>
> https://bugs.launchpad.net/qemu/+bug/1708462
>
> Currently most Python code in QEMU is for Python 2.6+ only. There
> have only been a few patches adding Python 3 support to certain
> scripts so far.
>
> In this email I want to highlight the most important scripts that need
> Python 3 support. Volunteers are welcome!
>
> Python scripts needed to build QEMU are the highest priority. They
> are invoked by ./configure or make. I've identified the following:
>
> scripts/signrom.py
> scripts/qapi*.py
> scripts/modules/module_block.py
> scripts/tracetool*
> I have tracetool on my todo list and hope to add Python 3 support in QEMU 2.11.
AFAICT tracetool seems to already work - i hacked rules.mak to
run tracetool via python3 and nothing obvious broke
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-08-09 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 10:16 [Qemu-devel] Making QEMU build with Python 3 Stefan Hajnoczi
2017-08-09 12:53 ` Philippe Mathieu-Daudé
2017-08-09 14:11 ` Stefan Hajnoczi
2017-08-09 13:10 ` Daniel P. Berrange [this message]
2017-08-09 13:51 ` Stefan Hajnoczi
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=20170809131032.GH24723@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ross@burtonini.com \
--cc=stefanha@gmail.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).