On 15 October 2018 at 19:01, Eduardo Habkost wrote:
> On Mon, Oct 15, 2018 at 05:55:27PM +0100, Peter Maydell wrote:
>> I also suspect "a few months" is an underestimate. My guess
>> would be we're going to want to keep Python 2 support for
>> at least the next year, maybe two.
>
> Python 2.7 will
Eduardo Habkost writes:
> On Mon, Oct 15, 2018 at 05:55:27PM +0100, Peter Maydell wrote:
>> On 15 October 2018 at 17:33, Markus Armbruster wrote:
>> > Kevin Wolf writes:
>> >
>> >> Am 15.10.2018 um 12:02 hat Peter Maydell geschrieben:
>> >> It's easier to port stuff to Python 3 though than maki
On 10/15/2018 08:33 PM, Eduardo Habkost wrote:
> On Mon, Oct 15, 2018 at 08:19:18PM +0200, Christian Borntraeger wrote:
[...]
It's easier to port stuff to Python 3 though than making them work with
both. I think Eduardo's RFC is in part motivated by a patch from
Philippe tha
On Mon, Oct 15, 2018 at 08:19:18PM +0200, Christian Borntraeger wrote:
>
>
> On 10/15/2018 06:33 PM, Markus Armbruster wrote:
> > Kevin Wolf writes:
> >
> >> Am 15.10.2018 um 12:02 hat Peter Maydell geschrieben:
> >>> On 15 October 2018 at 10:32, Daniel P. Berrangé
> >>> wrote:
> On Sat,
On 10/15/2018 06:33 PM, Markus Armbruster wrote:
> Kevin Wolf writes:
>
>> Am 15.10.2018 um 12:02 hat Peter Maydell geschrieben:
>>> On 15 October 2018 at 10:32, Daniel P. Berrangé wrote:
On Sat, Oct 13, 2018 at 02:02:27AM -0300, Eduardo Habkost wrote:
> Signed-off-by: Eduardo Habkos
On Mon, Oct 15, 2018 at 05:55:27PM +0100, Peter Maydell wrote:
> On 15 October 2018 at 17:33, Markus Armbruster wrote:
> > Kevin Wolf writes:
> >
> >> Am 15.10.2018 um 12:02 hat Peter Maydell geschrieben:
> >> It's easier to port stuff to Python 3 though than making them work with
> >> both. I th
On 15 October 2018 at 17:33, Markus Armbruster wrote:
> Kevin Wolf writes:
>
>> Am 15.10.2018 um 12:02 hat Peter Maydell geschrieben:
>> It's easier to port stuff to Python 3 though than making them work with
>> both. I think Eduardo's RFC is in part motivated by a patch from
>> Philippe that con
Kevin Wolf writes:
> Am 15.10.2018 um 12:02 hat Peter Maydell geschrieben:
>> On 15 October 2018 at 10:32, Daniel P. Berrangé wrote:
>> > On Sat, Oct 13, 2018 at 02:02:27AM -0300, Eduardo Habkost wrote:
>> >> Signed-off-by: Eduardo Habkost
>> >> ---
>> >> I'd like to do this in QEMU 3.1. I thi
On 15.10.18 13:01, Max Reitz wrote:
> On 15.10.18 07:55, Markus Armbruster wrote:
>> Max Reitz writes:
>>
>>> On 13.10.18 22:36, Eduardo Habkost wrote:
On Sat, Oct 13, 2018 at 08:20:25PM +0200, Max Reitz wrote:
> On 13.10.18 07:02, Eduardo Habkost wrote:
>> Signed-off-by: Eduardo Habk
On 15.10.18 07:55, Markus Armbruster wrote:
> Max Reitz writes:
>
>> On 13.10.18 22:36, Eduardo Habkost wrote:
>>> On Sat, Oct 13, 2018 at 08:20:25PM +0200, Max Reitz wrote:
On 13.10.18 07:02, Eduardo Habkost wrote:
> Signed-off-by: Eduardo Habkost
> ---
> I'd like to do this in
Am 15.10.2018 um 12:02 hat Peter Maydell geschrieben:
> On 15 October 2018 at 10:32, Daniel P. Berrangé wrote:
> > On Sat, Oct 13, 2018 at 02:02:27AM -0300, Eduardo Habkost wrote:
> >> Signed-off-by: Eduardo Habkost
> >> ---
> >> I'd like to do this in QEMU 3.1. I think it's time to drop
> >> su
On Mon, Oct 15, 2018 at 11:02:03AM +0100, Peter Maydell wrote:
> On 15 October 2018 at 10:32, Daniel P. Berrangé wrote:
> > On Sat, Oct 13, 2018 at 02:02:27AM -0300, Eduardo Habkost wrote:
> >> Signed-off-by: Eduardo Habkost
> >> ---
> >> I'd like to do this in QEMU 3.1. I think it's time to dro
On 15 October 2018 at 10:32, Daniel P. Berrangé wrote:
> On Sat, Oct 13, 2018 at 02:02:27AM -0300, Eduardo Habkost wrote:
>> Signed-off-by: Eduardo Habkost
>> ---
>> I'd like to do this in QEMU 3.1. I think it's time to drop
>> support for old systems that have only Python 2.
>>
>> We still have
On Sat, Oct 13, 2018 at 02:02:27AM -0300, Eduardo Habkost wrote:
> Signed-off-by: Eduardo Habkost
> ---
> I'd like to do this in QEMU 3.1. I think it's time to drop
> support for old systems that have only Python 2.
>
> We still have a few scripts that are not required for building
> QEMU that st
Max Reitz writes:
> On 13.10.18 22:36, Eduardo Habkost wrote:
>> On Sat, Oct 13, 2018 at 08:20:25PM +0200, Max Reitz wrote:
>>> On 13.10.18 07:02, Eduardo Habkost wrote:
Signed-off-by: Eduardo Habkost
---
I'd like to do this in QEMU 3.1. I think it's time to drop
support for
On 13.10.18 22:36, Eduardo Habkost wrote:
> On Sat, Oct 13, 2018 at 08:20:25PM +0200, Max Reitz wrote:
>> On 13.10.18 07:02, Eduardo Habkost wrote:
>>> Signed-off-by: Eduardo Habkost
>>> ---
>>> I'd like to do this in QEMU 3.1. I think it's time to drop
>>> support for old systems that have only
On Sat, Oct 13, 2018 at 08:20:25PM +0200, Max Reitz wrote:
> On 13.10.18 07:02, Eduardo Habkost wrote:
> > Signed-off-by: Eduardo Habkost
> > ---
> > I'd like to do this in QEMU 3.1. I think it's time to drop
> > support for old systems that have only Python 2.
> >
> > We still have a few script
On 13.10.18 07:02, Eduardo Habkost wrote:
> Signed-off-by: Eduardo Habkost
> ---
> I'd like to do this in QEMU 3.1. I think it's time to drop
> support for old systems that have only Python 2.
>
> We still have a few scripts that are not required for building
> QEMU that still work only with Pyt
On 10/13/18 12:02 AM, Eduardo Habkost wrote:
Signed-off-by: Eduardo Habkost
---
Commit message is sparse; can you do something like commit e7b3af81
where you call out the availability of python 3 on all the platforms
that are currently supported per our platforms doc?
I'd like to do this
Signed-off-by: Eduardo Habkost
---
I'd like to do this in QEMU 3.1. I think it's time to drop
support for old systems that have only Python 2.
We still have a few scripts that are not required for building
QEMU that still work only with Python 2 (iotests being the most
relevant set). Requiring
20 matches
Mail list logo
