Re: [PATCH] docs: sphinx/requirements: Limit jinja2<3.1

From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-doc@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] docs: sphinx/requirements: Limit jinja2<3.1
Date: Tue, 29 Mar 2022 09:31:43 -0600	[thread overview]
Message-ID: <871qyk7p28.fsf@meer.lwn.net> (raw)
In-Reply-To: <7dbff8a0-f4ff-34a0-71c7-1987baf471f9@gmail.com>

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... 

> 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.

Thanks,

jon