On 20/02/2023 20.56, John Snow wrote:
On Mon, Feb 20, 2023 at 1:16 AM Thomas Huth wrote:
On 17/02/2023 21.46, John Snow wrote:
On Thu, Feb 16, 2023 at 5:58 AM Thomas Huth wrote:
On 15/02/2023 20.05, Markus Armbruster wrote:
The discussion under PATCH 6 makes me think there's a bit of conf
On Mon, Feb 20, 2023 at 1:16 AM Thomas Huth wrote:
>
> On 17/02/2023 21.46, John Snow wrote:
> > On Thu, Feb 16, 2023 at 5:58 AM Thomas Huth wrote:
> >>
> >> On 15/02/2023 20.05, Markus Armbruster wrote:
> >>> The discussion under PATCH 6 makes me think there's a bit of confusion
> >>> about the
On 17/02/2023 21.46, John Snow wrote:
On Thu, Feb 16, 2023 at 5:58 AM Thomas Huth wrote:
On 15/02/2023 20.05, Markus Armbruster wrote:
The discussion under PATCH 6 makes me think there's a bit of confusion
about the actual impact of dropping support for Python 3.6. Possibly
because it's spel
On Thu, Feb 16, 2023 at 5:58 AM Thomas Huth wrote:
>
> On 15/02/2023 20.05, Markus Armbruster wrote:
> > The discussion under PATCH 6 makes me think there's a bit of confusion
> > about the actual impact of dropping support for Python 3.6. Possibly
> > because it's spelled out in the commit messa
On Fri, Feb 17, 2023 at 03:37:16PM +, Peter Maydell wrote:
> On Fri, 17 Feb 2023 at 09:56, Thomas Huth wrote:
> >
> > On 17/02/2023 10.06, Markus Armbruster wrote:
> > > Thomas Huth writes:
> > ...
> > > My view on all this is a bit more pragmatic.
> > >
> > > For a human developer, the diffe
On Fri, 17 Feb 2023 at 09:56, Thomas Huth wrote:
>
> On 17/02/2023 10.06, Markus Armbruster wrote:
> > Thomas Huth writes:
> ...
> > My view on all this is a bit more pragmatic.
> >
> > For a human developer, the difference between "dnf install
> > python-sphinx" and "pip install sphinx" is, in m
On 2/17/23 12:37, Daniel P. Berrangé wrote:
So basically I'm suggesting we take a combination of John's series
here, and Paolo's series. John's last patch would change so that our
dockerfiles grab docutils with pip instead of disabling docs build
on centos8. Then look at introducing the use of v
On Fri, Feb 17, 2023 at 02:46:53PM +0100, Thomas Huth wrote:
> On 17/02/2023 12.37, Daniel P. Berrangé wrote:
> ...
> > The long life enterprise distros are the pain point in unlocking the
> > new of python features. So the proposal is that, at a minimum, we
> > augment the current policy with word
On 17/02/2023 12.37, Daniel P. Berrangé wrote:
...
The long life enterprise distros are the pain point in unlocking the
new of python features. So the proposal is that, at a minimum, we
augment the current policy with words to the effect that:
* For long life cycle distributions, QEMU will fo
On Thu, Feb 09, 2023 at 07:31:40PM -0500, John Snow wrote:
> Howdy, this series increases our minimum python version to 3.7.
..snip...
So based on the discussion in this thread I see the following as the
key take aways:
* Use of newer Meson feature
We need newer meson in order to continue/f
On Fri, Feb 17, 2023 at 10:06:49AM +0100, Markus Armbruster wrote:
> Thomas Huth writes:
>
> > On 15/02/2023 20.05, Markus Armbruster wrote:
> >> The discussion under PATCH 6 makes me think there's a bit of confusion
> >> about the actual impact of dropping support for Python 3.6. Possibly
> >>
On 17/02/2023 10.06, Markus Armbruster wrote:
Thomas Huth writes:
...
My view on all this is a bit more pragmatic.
For a human developer, the difference between "dnf install
python-sphinx" and "pip install sphinx" is, in my opinion, close to
negligible. Really no comparison to "git-clone GCC
Thomas Huth writes:
> On 15/02/2023 20.05, Markus Armbruster wrote:
>> The discussion under PATCH 6 makes me think there's a bit of confusion
>> about the actual impact of dropping support for Python 3.6. Possibly
>> because it's spelled out in the commit message of PATCH 7. Let me
>> summarize
Peter Maydell writes:
> On Wed, 15 Feb 2023 at 19:05, Markus Armbruster wrote:
>>
>> The discussion under PATCH 6 makes me think there's a bit of confusion
>> about the actual impact of dropping support for Python 3.6. Possibly
>> because it's spelled out in the commit message of PATCH 7. Let
On 15/02/2023 20.05, Markus Armbruster wrote:
The discussion under PATCH 6 makes me think there's a bit of confusion
about the actual impact of dropping support for Python 3.6. Possibly
because it's spelled out in the commit message of PATCH 7. Let me
summarize it in one sentence:
*** All
On Wed, 15 Feb 2023 at 19:05, Markus Armbruster wrote:
>
> The discussion under PATCH 6 makes me think there's a bit of confusion
> about the actual impact of dropping support for Python 3.6. Possibly
> because it's spelled out in the commit message of PATCH 7. Let me
> summarize it in one sente
The discussion under PATCH 6 makes me think there's a bit of confusion
about the actual impact of dropping support for Python 3.6. Possibly
because it's spelled out in the commit message of PATCH 7. Let me
summarize it in one sentence:
*** All supported host systems continue to work ***
Evi
Am 14.02.2023 um 19:35 hat John Snow geschrieben:
> On Thu, Feb 9, 2023 at 7:31 PM John Snow wrote:
> >
> > Howdy, this series increases our minimum python version to 3.7.
> >
> > CI: https://gitlab.com/jsnow/qemu/-/pipelines/771780626
> > (All green!)
> > GL: https://gitlab.com/jsnow/qemu/-/c
On Thu, Feb 9, 2023 at 7:31 PM John Snow wrote:
>
> Howdy, this series increases our minimum python version to 3.7.
>
> CI: https://gitlab.com/jsnow/qemu/-/pipelines/771780626
> (All green!)
> GL: https://gitlab.com/jsnow/qemu/-/commits/python-require-37
>
> Patches 1 and 2 are loose pre-requi
First, a plea. Supporting 3.6 has made a few of us prisoners dragging
ball and chain. So, please, *please* let us cut of these leg irons!
The series does not include follow-up cleanups. Fine with me.
Howdy, this series increases our minimum python version to 3.7.
CI: https://gitlab.com/jsnow/qemu/-/pipelines/771780626
(All green!)
GL: https://gitlab.com/jsnow/qemu/-/commits/python-require-37
Patches 1 and 2 are loose pre-requisites; I'd like to merge them into
qemu.git within the week whe
21 matches
Mail list logo
