On 3/29/22 08:31, Jonathan Corbet wrote: > Akira Yokosawa <akiyks@xxxxxxxxx> 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@xxxxxxxxx> >> Cc: Jonathan Corbet <corbet@xxxxxxx> >> Cc: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx> >> Cc: linux-doc@xxxxxxxxxxxxxxx >> --- >> 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
