All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Daniel Berrangé" <berrange@redhat.com>
Subject: Re: CentOS 9, Python, and other Fairytales
Date: Thu, 19 Feb 2026 08:29:46 +0100	[thread overview]
Message-ID: <874ind6vit.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFn=p-ZdzRuisd6g65A+VXyDKXnTuBc0gnt0ApbhVBZG5GhJZQ@mail.gmail.com> (John Snow's message of "Wed, 18 Feb 2026 15:41:03 -0500")

John Snow <jsnow@redhat.com> writes:

> On Wed, Feb 18, 2026 at 3:26 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Il mer 18 feb 2026, 18:10 John Snow <jsnow@redhat.com> ha scritto:
>>> On Wed, Feb 18, 2026, 6:48 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>> Markus Armbruster <armbru@redhat.com> writes:
>>>>
>>>> > John Snow <jsnow@redhat.com> writes:

[...]

>>>> >> My plan:
>>>> >> - Wait and see what happens after the current QEMU release
>>>> >> - Gleefully drop Ubuntu 22.04 in April (Allows Python 3.11+)
>>>> >> - Gleefully drop Debian 12 in June
>>>> >> - Hold my breath and see if FreeBSD happens to modernize by this point
>>>> >> (They have until October 2027 to do so, so it's a dice roll if they
>>>> >> will or not)
>>>> >> - Do a big round of Python modernization all at once; either to 3.11
>>>> >> or 3.12 depending, and either to Sphinx 5.x or 7.x depending, pray for
>>>> >> forgiveness that I am removing CentOS stream 9's ability to build docs
>>>> >> offline so I don't have to wait another six months and then do another
>>>> >> big cleanup round
>>>>
>>>> The main nice features of 3.12 are improved f-strings, which are nice
>>>> but not really a necessity.
>>>>
>>>> If I read it correctly, https://www.freshports.org/lang/python says it
>>>> has 3.9 on PPC and 3.11 elsewhere, but
>>>> https://www.freshports.org/lang/python311 says 3.11 exists on PPC as well.
>>>>
>>>> I'd go for 3.11 and Sphinx 7.  For FreeBSD we can require Python from Ports.
>>>
>>>
>>> freebsd ports is currently at 3.11, which is the main reason I am saying "see what freebsd does by June"
>>>
>>> if they update, we can have Python 3.12 and Sphinx 7.x. If they don't, we get 3.11 and 5.x
>>
>>
>> Why can't we do 3.11 and 7.x, and let freebsd also get sphinx from pypi until they update?
>
> Hm, I guess no reason, beyond my recalcitrance on breaking docs on a
> supported build platform unless absolutely necessary. It'd still be my
> preference to align with the native distro repo/ports versions if at
> all possible, but I suppose if FreeBSD doesn't fix itself by June or
> so that we can consider dropping docs support with ports packages at
> that time.
>
> (I think I just have Stockholm Syndrome from arguing for "unnecessary
> version bumps to get shiny new toys" and prefer to let those arguments
> come from my seniors ... so I stick with very safe changes when at all
> possible.)

You do.  Please consider going to 7.x really, really seriously.

>>
>> Paolo
>>
>>> . Both are good jumps, but on the chance I can make the bigger jump, I'd rather do it in one round instead of two.
>>>
>>>>
>>>> Paolo
>>>>



      parent reply	other threads:[~2026-02-19  7:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 22:59 CentOS 9, Python, and other Fairytales John Snow
2026-02-18  6:54 ` Markus Armbruster
2026-02-18 11:48   ` Paolo Bonzini
2026-02-18 17:10     ` John Snow
2026-02-18 20:25       ` Paolo Bonzini
2026-02-18 20:41         ` John Snow
2026-02-18 21:23           ` Warner Losh
2026-02-19  7:30             ` Markus Armbruster
2026-02-19  7:29           ` Markus Armbruster [this message]

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=874ind6vit.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.