qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-stable@nongnu.org, "Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v2] docs/conf.py: Remove usage of distutils
Date: Mon, 4 Mar 2024 14:10:23 +0100	[thread overview]
Message-ID: <88668398-ee50-4fc6-8892-224c94e39f5d@redhat.com> (raw)
In-Reply-To: <20240304130403.129543-1-thuth@redhat.com>

On 04/03/2024 14.04, Thomas Huth wrote:
> The macOS jobs in our CI recently started failing, complaining that
> the distutils module is not available anymore. And indeed, according to
> https://peps.python.org/pep-0632/ it's been deprecated since a while
> and now likely got removed in recent Python versions.
> 
> Fortunately, we only use it for a version check via LooseVersion here
> which we don't really need anymore - according to Repology.org, these
> are the versions of sphinx-rtd-theme that are currently used by the
> various distros:
> 
>   centos_stream_8: 0.3.1
>   centos_stream_9: 0.5.1
>   fedora_38: 1.1.1
>   fedora_39: 1.2.2
>   freebsd: 1.0.0
>   haikuports_master: 1.2.1
>   openbsd: 1.2.2
>   opensuse_leap_15_5: 0.5.1
>   pkgsrc_current: 2.0.0
>   debian_11: 0.5.1
>   debian_12: 1.2.0
>   ubuntu_20_04: 0.4.3
>   ubuntu_22_04: 1.0.0
>   ubuntu_24_04: 2.0.0
> 
> So except for CentOS 8, all distros are using a newer version of
> sphinx-rtd-theme, and for CentOS 8 we don't support compiling with
> the Sphinx of the distro anymore anyway, since it's based on the
> Python 3.6 interpreter there. For compiling on CentOS 8, you have
> to use the alternative Python 3.8 interpreter which comes without
> Sphinx, so that needs the Sphinx installed via pip in the venv
> instead, and that is using a newer version, too, according to our
> pythondeps.toml file.

FWIW, here's a CI run with CentOS 8:

  https://gitlab.com/thuth/qemu/-/jobs/6309310171#L65

As you can see, it uses Python 3.8 with sphinx_rtd_theme 2.0.0, so I think 
we should be fine here, indeed.

  Thomas





  parent reply	other threads:[~2024-03-04 13:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 13:04 [PATCH v2] docs/conf.py: Remove usage of distutils Thomas Huth
2024-03-04 13:09 ` Michael Tokarev
2024-03-04 13:10 ` Thomas Huth [this message]
2024-03-04 16:56 ` Peter Maydell
2024-03-04 17:11   ` Thomas Huth
2024-03-04 18:04     ` Daniel P. Berrangé
2024-03-05 10:39       ` Thomas Huth
2024-03-09 17:27         ` Peter Maydell
2024-03-09 18:29           ` Philippe Mathieu-Daudé
2024-03-09 20:15             ` Peter Maydell
2024-03-10 14:10           ` Peter Maydell
2024-03-04 21:15 ` Alex Bennée
2024-03-05  9:44   ` Peter Maydell

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=88668398-ee50-4fc6-8892-224c94e39f5d@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).