All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	David Michael <fedora.dm0@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] scripts: Support building with Python 3
Date: Thu, 31 Aug 2017 13:50:27 +0100	[thread overview]
Message-ID: <CAFEAcA8tNXShUHB1L2g9u02CKmmJ+mX9nytSsi-HZ6Dmu0zxYg@mail.gmail.com> (raw)
In-Reply-To: <20170831110222.GH17315@redhat.com>

On 31 August 2017 at 12:02, Daniel P. Berrange <berrange@redhat.com> wrote:
> On Thu, Aug 31, 2017 at 11:55:18AM +0100, Peter Maydell wrote:
>> On 31 August 2017 at 11:47, Daniel P. Berrange <berrange@redhat.com> wrote:
>> > If we can update to python 2.7 as our minimum, then supporting py2
>> > and py3 gets simpler, avoiding some of the nastier hacks, even
>> > without that though it isn't too hard.
>>
>> Unfortunately RHEL6 is what's holding us to retaining 2.6
>> support, and googling suggests that doesn't go EOL until 2020...
>
> Who is actually requiring that we support RHEL6 until EOL though ?

OK, if we don't need to retain RHEL6 support that would help
(we should in that case not bother pulling in that big lump
of argument parsing code that just went past in a patchset
purely for the benefit of 2.6 support). How are the other
LTS distros for Python versions?

thanks
-- PMM

  parent reply	other threads:[~2017-08-31 12:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-20  5:58 [Qemu-devel] [PATCH] scripts: Support building with Python 3 David Michael
2017-08-21 14:29 ` Markus Armbruster
2017-08-30 17:09   ` Stefan Hajnoczi
2017-08-31  6:35     ` Markus Armbruster
2017-08-31 10:27       ` Peter Maydell
2017-08-31 10:47         ` Daniel P. Berrange
2017-08-31 10:55           ` Peter Maydell
2017-08-31 11:02             ` Daniel P. Berrange
2017-08-31 12:44               ` Markus Armbruster
2017-08-31 13:22                 ` Kashyap Chamarthy
2017-08-31 12:50               ` Peter Maydell [this message]
2017-08-31 12:58         ` Markus Armbruster
2017-08-31 13:14           ` Daniel P. Berrange
2017-08-31 13:19             ` Peter Maydell
2017-08-31 13:25               ` Daniel P. Berrange
2017-08-31 13:32                 ` Peter Maydell
2017-09-01 19:26             ` Max Reitz
2017-08-31 13:29           ` Peter Maydell
2017-08-30 17:15 ` Stefan Hajnoczi
2017-09-18 15:36 ` Stefan Hajnoczi
2017-10-02  6:17   ` Markus Armbruster

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=CAFEAcA8tNXShUHB1L2g9u02CKmmJ+mX9nytSsi-HZ6Dmu0zxYg@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=fedora.dm0@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --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 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.