From: Peter Maydell <peter.maydell@linaro.org>
To: John Snow <jsnow@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] Deprecation policy and build dependencies
Date: Mon, 3 Jun 2019 19:27:00 +0100 [thread overview]
Message-ID: <CAFEAcA-+2Csn4wW8xLaogJrQiqc2xHrGKFc_zdaOMKNn-yas9g@mail.gmail.com> (raw)
In-Reply-To: <b4de3161-7b9c-debc-a652-21832612ebf4@redhat.com>
On Mon, 3 Jun 2019 at 19:21, John Snow <jsnow@redhat.com> wrote:
> I get it, we don't want to require Python 3.8 because some dev wanted
> assignment conditionals -- but we're talking about Python 2 here, which
> suffers its EOL by the end of this calendar year.
>
> So do we think it's reasonable to drop support for Python2 for the
> release that comes out after Python2's EOL, or do we insist on 2x3
> simultaneous support for years more?
I don't have a strong opinion on Python in particular, but
I think it would be nicer to avoid the "python is a special
snowflake" effect. Would it really be so bad for it to just
be "drop it when it falls off the last LTS distro" like the
rest of our dependencies ?
thanks
-- PMM
next prev parent reply other threads:[~2019-06-03 18:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 19:24 [Qemu-devel] Deprecation policy and build dependencies Eduardo Habkost
2019-05-31 22:06 ` John Snow
2019-06-03 12:26 ` Markus Armbruster
2019-06-03 18:02 ` John Snow
2019-06-03 18:16 ` Cornelia Huck
2019-06-03 19:44 ` Eduardo Habkost
2019-06-04 7:14 ` Philippe Mathieu-Daudé
2019-06-03 18:17 ` Peter Maydell
2019-06-03 18:21 ` John Snow
2019-06-03 18:27 ` Peter Maydell [this message]
2019-06-03 18:38 ` John Snow
2019-06-04 5:31 ` Markus Armbruster
2019-06-04 15:51 ` John Snow
2019-06-04 5:26 ` Gerd Hoffmann
2019-06-05 15:50 ` Daniel P. Berrangé
2019-06-05 20:13 ` Eduardo Habkost
2019-06-05 20:42 ` Eric Blake
2019-06-05 20:49 ` Eduardo Habkost
2019-06-05 22:02 ` Eric Blake
2019-06-06 5:22 ` Markus Armbruster
2019-06-06 9:19 ` Daniel P. Berrangé
2019-06-05 15:44 ` Daniel P. Berrangé
2019-06-05 18:13 ` Eduardo Habkost
2019-06-06 9:23 ` Daniel P. Berrangé
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=CAFEAcA-+2Csn4wW8xLaogJrQiqc2xHrGKFc_zdaOMKNn-yas9g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).