All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>, Jonathan Corbet <corbet@lwn.net>
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 23:01:37 +0900	[thread overview]
Message-ID: <7de98030-c154-416c-ef80-17a2fd812dd1@gmail.com> (raw)
In-Reply-To: <02a00556-d885-7532-64ad-14027a4b5e33@gmail.com>

On Tue, 29 Mar 2022 20:01:46 +0700,
Bagas Sanjaya wrote:
> On 29/03/22 13.07, Akira Yokosawa wrote:
>> diff --git a/Documentation/sphinx/requirements.txt b/Documentation/sphinx/requirements.txt
>> index 9a35f50798a6..2c573541ab71 100644
>> --- a/Documentation/sphinx/requirements.txt
>> +++ b/Documentation/sphinx/requirements.txt
>> @@ -1,2 +1,4 @@
>> +# jinja2>=3.1 is not compatible with Sphinx<4.0
>> +jinja2<3.1
>>   sphinx_rtd_theme
>>   Sphinx==2.4.4
>>
> 
> I see that we had already pinned the exact Sphinx version to 2.4.4 (or am
> I read the requirements wrong?), so this only matters when people use Sphinx
> from distribution packages, rather than using virtualenv as recommended.

On the contrary!

This matters when you do fresh-install of Sphinx 2.4.4 using virtualenv.
Please try it without the limit of inja2<3.1.
If you can't reproduce the breakage, I might be missing something
something important.

I guess you had your Sphinx installed before jinja2 3.1.0
was released (March 24, 2022), didn't you?

        Thanks, Akira


  parent reply	other threads:[~2022-03-29 14:01 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 [this message]
2022-03-29 15:31 ` Jonathan Corbet
2022-03-29 15:36   ` Randy Dunlap
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=7de98030-c154-416c-ef80-17a2fd812dd1@gmail.com \
    --to=akiyks@gmail.com \
    --cc=bagasdotme@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.