Re: Proposed way forward Re: [PATCH v2 0/7] Python: Drop support for Python 3.6

2023-02-17 Thread Paolo Bonzini
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

Re: Proposed way forward Re: [PATCH v2 0/7] Python: Drop support for Python 3.6

2023-02-17 Thread Daniel P . Berrangé
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

Re: Proposed way forward Re: [PATCH v2 0/7] Python: Drop support for Python 3.6

2023-02-17 Thread Thomas Huth
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

Proposed way forward Re: [PATCH v2 0/7] Python: Drop support for Python 3.6

2023-02-17 Thread Daniel P . Berrangé
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