From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>, Akira Yokosawa <akiyks@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: sphinx/requirements: Limit jinja2<3.1
Date: Tue, 29 Mar 2022 08:36:23 -0700 [thread overview]
Message-ID: <42ae72ad-70db-719b-ed0b-8afedf50121d@infradead.org> (raw)
In-Reply-To: <871qyk7p28.fsf@meer.lwn.net>
On 3/29/22 08:31, Jonathan Corbet wrote:
> Akira Yokosawa <akiyks@gmail.com> writes:
>
>> jinja2 release 3.1.0 (March 24, 2022) broke Sphinx<4.0.
>> This looks like the result of deprecating Python 3.6.
>> It has been tested against Sphinx 4.3.0 and later later.
>
> *Sigh*. I wish this stuff didn't feel like such a house of cards
> sometimes...
ack.
>> Setting an upper limit of <3.1 to junja2 can unbreak Sphinx<4.0
>> including Sphinx 2.4.4.
>>
>> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
>> Cc: linux-doc@vger.kernel.org
>> ---
>> Or we can bump the requirement to Sphinx>=4.0.
>> Thoughts?
>
> It's probably time to consider a bump there, but that is a bigger one
> than I would want to do at this point. So I'll just fast-track this
> patch in; dropping it into the stable updates probably makes sense too.
Yeah, some of us don't have Python4 installed...
--
~Randy
next prev parent reply other threads:[~2022-03-29 15:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 6:07 [PATCH] docs: sphinx/requirements: Limit jinja2<3.1 Akira Yokosawa
2022-03-29 13:01 ` Bagas Sanjaya
2022-03-29 14:00 ` Jonathan Corbet
2022-03-29 14:08 ` Akira Yokosawa
2022-03-29 14:01 ` Akira Yokosawa
2022-03-29 15:31 ` Jonathan Corbet
2022-03-29 15:36 ` Randy Dunlap [this message]
2022-03-29 23:51 ` Akira Yokosawa
2022-03-30 0:07 ` Randy Dunlap
2022-03-30 0:25 ` Mauro Carvalho Chehab
2022-03-30 14:59 ` Akira Yokosawa
2022-03-30 17:07 ` Mauro Carvalho Chehab
2022-03-31 14:32 ` Akira Yokosawa
2022-05-21 7:58 ` "WARNING: Duplicate C declaration" from recent Sphinx (was Re: [PATCH] docs: sphinx/requirements: Limit jinja2<3.1) Akira Yokosawa
2022-05-21 9:46 ` Mauro Carvalho Chehab
2022-05-21 9:59 ` Akira Yokosawa
2022-05-22 0:57 ` Akira Yokosawa
2022-05-22 5:07 ` Mauro Carvalho Chehab
2022-05-22 9:28 ` Akira Yokosawa
2022-03-30 1:29 ` [PATCH] docs: sphinx/requirements: Limit jinja2<3.1 Akira Yokosawa
2022-03-30 19:44 ` 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=42ae72ad-70db-719b-ed0b-8afedf50121d@infradead.org \
--to=rdunlap@infradead.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.