Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: linux-doc@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] docs: kernel_include.py: Cope with docutils 0.21
Date: Thu, 02 May 2024 08:52:28 -0600	[thread overview]
Message-ID: <87edak8dw3.fsf@meer.lwn.net> (raw)
In-Reply-To: <376c813f-971c-4558-b596-64e7f6f3833d@gmail.com>

Akira Yokosawa <akiyks@gmail.com> writes:

> Hi Jon,
>
> On Wed, 1 May 2024 12:16:11 +0900, Akira Yokosawa wrote:
>> Running "make htmldocs" on a newly installed Sphinx 7.3.7 ends up in
>> a build error:
>> 
>>     Sphinx parallel build error:
>>     AttributeError: module 'docutils.nodes' has no attribute 'reprunicode'
>> 
>> docutils 0.21 has removed nodes.reprunicode, quote from release note [1]:
>> 
>>   * Removed objects:
>> 
>>     docutils.nodes.reprunicode, docutils.nodes.ensure_str()
>>         Python 2 compatibility hacks
>> 
>> Sphinx 7.3.0 supports docutils 0.21 [2]:
>> 
>> kernel_include.py, whose origin is misc.py of docutils, uses reprunicode.
>> 
>> Upstream docutils removed the offending line from the corresponding file
>> (docutils/docutils/parsers/rst/directives/misc.py) in January 2022.
>> Quoting the changelog [3]:
>> 
>>     Deprecate `nodes.reprunicode` and `nodes.ensure_str()`.
>> 
>>     Drop uses of the deprecated constructs (not required with Python 3).
>> 
>> Do the same for kernel_include.py.
>> 
>> Tested against:
>>   - Sphinx 2.4.5 (docutils 0.17.1)
>>   - Sphinx 3.4.3 (docutils 0.17.1)
>>   - Sphinx 5.3.0 (docutils 0.18.1)
>>   - Sphinx 6.2.1 (docutils 0.19)
>>   - Sphinx 7.2.6 (docutils 0.20.1)
>>   - Sphinx 7.3.7 (docutils 0.21.2)
>> 
>> Link: http://www.docutils.org/RELEASE-NOTES.html#release-0-21-2024-04-09 [1]
>> Link: https://www.sphinx-doc.org/en/master/changes.html#release-7-3-0-released-apr-16-2024 [2]
>> Link: https://github.com/docutils/docutils/commit/c8471ce47a24 [3]
>> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
>
> I forgot to put a Cc: stable@ tag.
>
> Jon, could you do it for me?
> I'm not sure how far this wants to be backported.
> Maybe v6.1?  It's up to you!

I was planning to do that, yes.  I'll try to get to the queue today.

Thanks,

jon

  reply	other threads:[~2024-05-02 14:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01  3:16 [PATCH] docs: kernel_include.py: Cope with docutils 0.21 Akira Yokosawa
2024-05-01  7:49 ` Bagas Sanjaya
2024-05-02 14:46 ` Akira Yokosawa
2024-05-02 14:52   ` Jonathan Corbet [this message]
2024-05-02 16:01 ` Jonathan Corbet

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=87edak8dw3.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --cc=linux-doc@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