qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH 0/2] docs, python: bump sphinx preferred version
Date: Tue, 15 Jul 2025 18:20:21 -0400	[thread overview]
Message-ID: <CAFn=p-bZBok_n-evUwjm6cdCmr+4ofjTRbVRJ+DNxft9gV4PpA@mail.gmail.com> (raw)
In-Reply-To: <20250715212848.171879-1-jsnow@redhat.com>

fwiw, I think this is important enough / harmless enough to sneak into
the rc releases, if possible.

On Tue, Jul 15, 2025 at 5:28 PM John Snow <jsnow@redhat.com> wrote:
>
> CI: https://gitlab.com/jsnow/qemu/-/pipelines/1928836481
>
> Unlike the previous series, this series only adjusts the *preferred*
> sphinx version to be higher, leaving the accepted version at 3.4.3, the
> version that CentOS Stream 9 still ships with.
>
> Unfortunately, this means we can't cut out the compatibility code for
> sphinx we're still carrying around just yet, but we'll await that
> glorious moment to arrive on some future day.
>
> Sphinx 6.2.1 is being chosen as the new default because it still offers
> support for Python 3.8+, but is new enough to support Python 3.13+.
>
> Distro version information for supported platforms as of 2025-07-15:
>
> distro              python3  pip     setuptools  sphinx
> -------------------------------------------------------
> alpine_3_19         3.11.13  23.3.1  70.3.0      6.2.1
> alpine_3_20         3.12.11  24.0    70.3.0      7.2.6
> alpine_3_21         3.12.11  24.3.1  70.3.0      8.1.3
> alpine_3_22         3.12.11  25.1.1  80.9.0      8.2.3
> centos_stream_9     3.9.23   21.3.1  53.0.0      3.4.3
> centos_stream_10    3.12.11  23.3.2  69.0.3      7.2.6
> debian_12           3.11.2   23.0.1  66.1.1      5.3.0
> fedora_41           3.13.5   24.2    69.2.0      7.3.7
> fedora_42           3.13.5   24.3.1  74.1.3      8.1.3
> freebsd             3.11.13  23.3.2  63.1.0      5.3.0
> homebrew            3.13.5   ---     80.9.0      8.2.3
> macports            3.13.5   25.1.1  78.1.1      8.2.3
> openbsd             3.12.11  25.1.1  79.0.1      8.2.3
> pkgsrc_current      3.12.11  25.1.1  80.9.0      8.2.3
> ubuntu_22_04        3.10.12  22.0.2  59.6.0      4.3.2
> ubuntu_24_04        3.12.3   24.0    68.1.2      7.2.6
> ubuntu_24_10        3.12.7   24.2    74.1.2      7.4.7
> ubuntu_25_04        3.13.3   25.0    75.8.0      8.1.3
>
> Akihiko Odaki (2):
>   docs: Bump sphinx to 6.2.1
>   MAINTAINERS: Add docs/requirements.txt
>
>  MAINTAINERS           | 1 +
>  docs/requirements.txt | 4 ++--
>  pythondeps.toml       | 4 ++--
>  3 files changed, 5 insertions(+), 4 deletions(-)
>
> --
> 2.50.0
>
>



  parent reply	other threads:[~2025-07-15 22:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 21:28 [PATCH 0/2] docs, python: bump sphinx preferred version John Snow
2025-07-15 21:28 ` [PATCH 1/2] docs: Bump sphinx to 6.2.1 John Snow
2025-07-15 21:28 ` [PATCH 2/2] MAINTAINERS: Add docs/requirements.txt John Snow
2025-07-15 22:20 ` John Snow [this message]
2025-07-16  5:10   ` [PATCH 0/2] docs, python: bump sphinx preferred version Thomas Huth
2025-07-16 15:04 ` Markus Armbruster
2025-07-16 15:15   ` John Snow
2025-07-16 17:03     ` Markus Armbruster

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='CAFn=p-bZBok_n-evUwjm6cdCmr+4ofjTRbVRJ+DNxft9gV4PpA@mail.gmail.com' \
    --to=jsnow@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).