On Wed, Jun 05, 2019 at 03:13:08PM -0300, Eduardo Habkost wrote:
> On Wed, Jun 05, 2019 at 04:44:03PM +0100, Daniel P. Berrangé wrote:
> [...]
> > Thus to answer your python 2 question, we should ask which of our build
> > targets cannot support python 3 ?
> >
> > Obviously we know the answer to t
On Wed, Jun 05, 2019 at 03:42:39PM -0500, Eric Blake wrote:
> On 6/5/19 3:13 PM, Eduardo Habkost wrote:
>
> >> IOW, I don't think RHEL-7 support as a build platform blocks us from
> >> dropping py2. We merely need to tweak our build platforms doc to clarify
> >> our intent wrt add-on yum repos.
>
Eric Blake writes:
> On 6/5/19 3:13 PM, Eduardo Habkost wrote:
>
>>> IOW, I don't think RHEL-7 support as a build platform blocks us from
>>> dropping py2. We merely need to tweak our build platforms doc to clarify
>>> our intent wrt add-on yum repos.
>>
>> If we clarify the docs in QEMU 4.1, is
On 6/5/19 3:49 PM, Eduardo Habkost wrote:
> On Wed, Jun 05, 2019 at 03:42:39PM -0500, Eric Blake wrote:
>> On 6/5/19 3:13 PM, Eduardo Habkost wrote:
>>
IOW, I don't think RHEL-7 support as a build platform blocks us from
dropping py2. We merely need to tweak our build platforms doc to cla
On Wed, Jun 05, 2019 at 03:42:39PM -0500, Eric Blake wrote:
> On 6/5/19 3:13 PM, Eduardo Habkost wrote:
>
> >> IOW, I don't think RHEL-7 support as a build platform blocks us from
> >> dropping py2. We merely need to tweak our build platforms doc to clarify
> >> our intent wrt add-on yum repos.
>
On 6/5/19 3:13 PM, Eduardo Habkost wrote:
>> IOW, I don't think RHEL-7 support as a build platform blocks us from
>> dropping py2. We merely need to tweak our build platforms doc to clarify
>> our intent wrt add-on yum repos.
>
> If we clarify the docs in QEMU 4.1, is there anything that
> preven
On Wed, Jun 05, 2019 at 04:50:06PM +0100, Daniel P. Berrangé wrote:
> On Mon, Jun 03, 2019 at 02:26:49PM +0200, Markus Armbruster wrote:
> > John Snow writes:
> >
> > > On 5/31/19 3:24 PM, Eduardo Habkost wrote:
> > >> Long story short: I would really like to drop support for Python
> > >> 2 in Q
On Wed, Jun 05, 2019 at 04:44:03PM +0100, Daniel P. Berrangé wrote:
[...]
> Thus to answer your python 2 question, we should ask which of our build
> targets cannot support python 3 ?
>
> Obviously we know the answer to that is RHEL-7. Except there is some
> fuzziness in there because it depends o
On Mon, Jun 03, 2019 at 02:26:49PM +0200, Markus Armbruster wrote:
> John Snow writes:
>
> > On 5/31/19 3:24 PM, Eduardo Habkost wrote:
> >> Long story short: I would really like to drop support for Python
> >> 2 in QEMU 4.1.
>
> The sooner, the better, as far as I'm concerned.
>
> >> What exac
On Fri, May 31, 2019 at 04:24:29PM -0300, Eduardo Habkost wrote:
> Long story short: I would really like to drop support for Python
> 2 in QEMU 4.1.
>
> What exactly prevents us from doing this? Does our deprecation
> policy really apply to build dependencies?
In general I do *not* consider our
On 6/4/19 1:31 AM, Markus Armbruster wrote:
> Peter Maydell writes:
>
>> On Mon, 3 Jun 2019 at 19:21, John Snow 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 t
On 6/3/19 8:16 PM, Cornelia Huck wrote:
> On Mon, 3 Jun 2019 14:02:16 -0400
> John Snow wrote:
[...]
>> I would rather not support Python2 a day after the clock expires.
>>
>>> I didn't bother checking Debian, Ubuntu LTS and SLES.
>>>
>>> For hosts other than Linux, we're less ambitious.
>>>
>>
Peter Maydell writes:
> On Mon, 3 Jun 2019 at 19:21, John Snow 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.
"Not because some dev wa
Hi,
> >> Normally I'd say it's only nice to also follow the depreciation policy
> >> for tooling as well to give people a chance to switch away, but with
> >> regards to Python2, I feel like we're in the clear to drop it for the
> >> first release that will happen after the Python2 doomsday cloc
On Mon, Jun 03, 2019 at 08:16:29PM +0200, Cornelia Huck wrote:
> On Mon, 3 Jun 2019 14:02:16 -0400
> John Snow wrote:
>
> > On 6/3/19 8:26 AM, Markus Armbruster wrote:
> > > John Snow writes:
> > >
> > >> On 5/31/19 3:24 PM, Eduardo Habkost wrote:
> > >>> Long story short: I would really li
On Mon, 3 Jun 2019 at 19:21, John Snow 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
On 6/3/19 2:27 PM, Peter Maydell wrote:
> On Mon, 3 Jun 2019 at 19:21, John Snow 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.
>>
>>
On 6/3/19 2:17 PM, Peter Maydell wrote:
> On Mon, 3 Jun 2019 at 19:02, John Snow wrote:
>> That policy strikes me as weird, because RHEL7 is not going to be, in
>> general, using the latest and greatest QEMU. Usually stable versions of
>> distros stick with the versions of the programs that cam
On Mon, 3 Jun 2019 at 19:02, John Snow wrote:
> That policy strikes me as weird, because RHEL7 is not going to be, in
> general, using the latest and greatest QEMU. Usually stable versions of
> distros stick with the versions of the programs that came out at the time.
>
> What's the benefit of mak
On Mon, 3 Jun 2019 14:02:16 -0400
John Snow wrote:
> On 6/3/19 8:26 AM, Markus Armbruster wrote:
> > John Snow writes:
> >
> >> On 5/31/19 3:24 PM, Eduardo Habkost wrote:
> >>> Long story short: I would really like to drop support for Python
> >>> 2 in QEMU 4.1.
> >
> > The sooner, the b
On 6/3/19 8:26 AM, Markus Armbruster wrote:
> John Snow writes:
>
>> On 5/31/19 3:24 PM, Eduardo Habkost wrote:
>>> Long story short: I would really like to drop support for Python
>>> 2 in QEMU 4.1.
>
> The sooner, the better, as far as I'm concerned.
>
>>> What exactly prevents us from doi
John Snow writes:
> On 5/31/19 3:24 PM, Eduardo Habkost wrote:
>> Long story short: I would really like to drop support for Python
>> 2 in QEMU 4.1.
The sooner, the better, as far as I'm concerned.
>> What exactly prevents us from doing this? Does our deprecation
>> policy really apply to buil
On 5/31/19 3:24 PM, Eduardo Habkost wrote:
> Long story short: I would really like to drop support for Python
> 2 in QEMU 4.1.
>
> What exactly prevents us from doing this? Does our deprecation
> policy really apply to build dependencies?
>
Normally I'd say it's only nice to also follow the
Long story short: I would really like to drop support for Python
2 in QEMU 4.1.
What exactly prevents us from doing this? Does our deprecation
policy really apply to build dependencies?
--
Eduardo
24 matches
Mail list logo
