From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
mchehab@kernel.org, mliska@suse.cz,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] docs: Fix the docs build with Sphinx 6.0
Date: Sat, 7 Jan 2023 14:17:24 +0900 [thread overview]
Message-ID: <cb916eae-fdf6-504f-8f38-7928e0fa8344@gmail.com> (raw)
In-Reply-To: <87wn629ggg.fsf@meer.lwn.net>
On Wed, 04 Jan 2023 13:45:35 -0700, Jonathan Corbet wrote:
> Sphinx 6.0 removed the execfile_() function, which we use as part of the
> configuration process. They *did* warn us... Just open-code the
> functionality as is done in Sphinx itself.
>
> Tested (using SPHINX_CONF, since this code is only executed with an
> alternative config file) on various Sphinx versions from 2.5 through 6.0.
>
> Reported-by: Martin Liška <mliska@suse.cz>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
I have tested full builds of documentation with this change
with Sphinx versions 1.7.9, 2.4.5, 3.4.3, 4.5.0, 5.3.0, and 6.0.0.
Tested-by: Akira Yokosawa <akiyks@gmail.com>
That said, Sphinx 6.0.0 needs much more time and memory than earlier
versions.
FYI, I needed to limit parallel slot to 2 (make -j2) on a 16GB machine.
If you are lucky, -j3 and -j4 might succeed. -j5 or more ended up in
OOM situations for me:
Comparison of elapsed time and maxresident with -j2:
============== ============ ===========
Sphinx version elapsed time maxresident
============== ============ ===========
5.3.0 10:16.81 937660
6.0.0 17:29.07 5292392
============== ============ ===========
Thanks, Akira
> ---
> Documentation/sphinx/load_config.py | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/sphinx/load_config.py b/Documentation/sphinx/load_config.py
> index eeb394b39e2c..8b416bfd75ac 100644
> --- a/Documentation/sphinx/load_config.py
> +++ b/Documentation/sphinx/load_config.py
> @@ -3,7 +3,7 @@
>
> import os
> import sys
> -from sphinx.util.pycompat import execfile_
> +from sphinx.util.osutil import fs_encoding
>
> # ------------------------------------------------------------------------------
> def loadConfig(namespace):
> @@ -48,7 +48,9 @@ def loadConfig(namespace):
> sys.stdout.write("load additional sphinx-config: %s\n" % config_file)
> config = namespace.copy()
> config['__file__'] = config_file
> - execfile_(config_file, config)
> + with open(config_file, 'rb') as f:
> + code = compile(f.read(), fs_encoding, 'exec')
> + exec(code, config)
> del config['__file__']
> namespace.update(config)
> else:
> --
> 2.38.1
next prev parent reply other threads:[~2023-01-07 5:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 20:45 Jonathan Corbet
2023-01-07 5:17 ` Akira Yokosawa [this message]
2023-01-08 14:01 ` Mauro Carvalho Chehab
2023-01-09 14:14 ` Martin Liška
2023-01-09 15:17 ` Akira Yokosawa
2023-01-11 23:13 ` Akira Yokosawa
2023-01-12 16:22 ` Martin Liška
2023-01-14 1:06 ` Akira Yokosawa
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=cb916eae-fdf6-504f-8f38-7928e0fa8344@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mliska@suse.cz \
/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®