From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3 15/15] docs: conf.py: Check Sphinx and docutils version
Date: Sun, 22 Jun 2025 20:06:13 +0200 [thread overview]
Message-ID: <20250622200613.5ad18093@foz.lan> (raw)
In-Reply-To: <c05dd5dc-1e30-4a2c-80dc-70e8b62cc681@gmail.com>
Em Sun, 22 Jun 2025 20:19:52 +0900
Akira Yokosawa <akiyks@gmail.com> escreveu:
> > After check Sphinx release notes, it seems that the
> > version compatibility is given by:
> >
> > ======= ============ ============
> > Sphinx Min Docutils Max Docutils
> > Version Version Version
> > ------- ------------ ------------
> > 3.4.3 >= 0.12.0 < 0.18.0
> > 4.0.0 >= 0.12.0 < 0.19.0
> > 6.0.0 >= 0.18.0 < 0.20.0
> > 7.0.0 >= 0.18.1 < 0.21.0
> > 7.2.0 >= 0.18.1 < 0.20.0
> > 7.4.0 >= 0.18.1 < 0.21.0
> > 8.0.0 >= 0.20.0 < 0.22.0
> > 8.2.3 >= 0.20.0 < 0.22.0
> > ======= ============ ============
> >
>
> <nitpick>
> So this is what I see in the changelog (not looked into < 6.0.0):
>
> ================= ====================
> Sphinx version docutils version
> (since) min max
> ----------------- ------------ -------
> 6.0.0 >= 0.18 < 0.20
> 6.2.0 >= 0.18.1 < 0.20
> 7.0.1 >= 0.18.1 < 0.21
> 7.3.0 >= 0.18.1 < 0.22
> 7.4.0 >= 0.20 < 0.22
> (up to 8.2.3)
> ================= ====================
>
> This Looks quite different from yours ...
> </nitpick>
Thanks for your feedback!
Getting this right is not too easy, specially since not all
changelog mentions docutil version. Btw, one of the factors I
used when building my table were to check the release dates
of Sphinx and docutils. So, I manually adjusted some entries,
as changelog usually say something like:
Release 5.0.0 (released May 30, 2022)¶
Dependencies
5.0.0 b1
#10164: Support Docutils 0.18. Patch by Adam Turner.
But doesn't mention minimal supported version.
I'll re-check and adjust it as needed, if Jon decides to pick it.
Thanks,
Mauro
next prev parent reply other threads:[~2025-06-22 18:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 6:02 [PATCH v3 00/15] Some improvements and fixes for the doc build system Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 01/15] docs: conf.py: properly handle include and exclude patterns Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 02/15] docs: Makefile: disable check rules on make cleandocs Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 03/15] scripts: scripts/test_doc_build.py: add script to test doc build Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 04/15] scripts: test_doc_build.py: make capture assynchronous Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 05/15] scripts: test_doc_build.py: better control its output Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 06/15] scripts: test_doc_build.py: better adjust to python version Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 07/15] scripts: test_doc_build.py: improve dependency list Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 08/15] scripts: test_doc_build.py: improve cmd.log logic Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 09/15] scripts: test_doc_build.py: make the script smarter Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 10/15] scripts: sphinx-pre-install: properly handle SPHINXBUILD Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 11/15] scripts: sphinx-pre-install: fix release detection for Fedora Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 12/15] scripts: test_doc_build.py: regroup and rename arguments Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 13/15] docs: sphinx: add a file with the requirements for lowest version Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 14/15] docs: conf.py: several coding style fixes Mauro Carvalho Chehab
2025-06-22 20:55 ` Jonathan Corbet
2025-06-22 21:41 ` Mauro Carvalho Chehab
2025-06-22 6:02 ` [PATCH v3 15/15] docs: conf.py: Check Sphinx and docutils version Mauro Carvalho Chehab
2025-06-22 11:19 ` Akira Yokosawa
2025-06-22 17:53 ` Mauro Carvalho Chehab
2025-06-22 18:06 ` Mauro Carvalho Chehab [this message]
2025-06-22 20:58 ` Jonathan Corbet
2025-06-22 21:50 ` Mauro Carvalho Chehab
2025-06-25 18:37 ` Jonathan Corbet
2025-06-25 20:18 ` Mauro Carvalho Chehab
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=20250622200613.5ad18093@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®