From: Eric Blake <eblake@redhat.com>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Ishani Chugh <chugh.ishani@research.iiit.ac.in>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] scripts: add argparse module for Python 2.6 compatibility
Date: Fri, 25 Aug 2017 12:42:44 -0500 [thread overview]
Message-ID: <4f21291d-d696-9651-e317-78ec4f08cbda@redhat.com> (raw)
In-Reply-To: <CAFEAcA_skx8s28zo38uTwM-TcJvX1pC6oTAxjy3q_AVN3JwHBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On 08/25/2017 11:40 AM, Peter Maydell wrote:
> Our choices about our dependencies are generally driven by "what
> are the versions available on the oldest distros which we wish
> to support building QEMU on", which typically is whatever the
> long-term-support versions of Ubuntu, SUSE, Redhat, etc are.
>
> Has somebody checked what that means for our Python version
> requirements?
At least this one:
RHEL/CentOS 6: Python-2.6.6
> (It would certainly be nicer if we could get away
> with bumping the version-req rather than including a big lump
> of code with yet-another-software-license, but maybe we can't.)
Based on the above, no sooner than when Red Hat is done supporting RHEL
6 (well, upstream can always decide to bump the minimum requirements it
and make Red Hat do the downstream back-compat work in isolation, but
there's enough Red Hat contributors that it shouldn't surprise anyone
that back-compat work patches will still be posted upstream...)
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-25 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 15:57 [Qemu-devel] [PATCH 0/3] scripts: add argparse module for Python 2.6 compatibility Stefan Hajnoczi
2017-08-25 15:57 ` [Qemu-devel] [PATCH 1/3] " Stefan Hajnoczi
2017-08-25 15:57 ` [Qemu-devel] [PATCH 2/3] docker.py: Python 2.6 argparse compatibility Stefan Hajnoczi
2017-08-26 0:29 ` Fam Zheng
2017-08-25 15:57 ` [Qemu-devel] [PATCH 3/3] tests: migration/guestperf " Stefan Hajnoczi
2017-08-25 16:24 ` [Qemu-devel] [PATCH 0/3] scripts: add argparse module for Python 2.6 compatibility no-reply
2017-08-29 9:59 ` Stefan Hajnoczi
2017-08-25 16:35 ` Philippe Mathieu-Daudé
2017-08-25 16:40 ` Peter Maydell
2017-08-25 17:42 ` Eric Blake [this message]
2017-08-29 10:01 ` Stefan Hajnoczi
2017-08-29 18:02 ` Philippe Mathieu-Daudé
2017-08-28 21:47 ` John Snow
2017-08-30 11:02 ` 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=4f21291d-d696-9651-e317-78ec4f08cbda@redhat.com \
--to=eblake@redhat.com \
--cc=chugh.ishani@research.iiit.ac.in \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.