Pin jinja2 in CI (#1490)

The 3.1 release of Jinja breaks some part of the Sphinx/nbsphinx
pipeline, causing tutorial jobs to fail.  The jinja2 developers consider
this a Sphinx bug, so we need to pin Jinja until a new version of Sphinx
or the nbsphinx extension is released to fix the issue.
This commit is contained in:
Jake Lishman 2022-03-25 14:23:06 +00:00 committed by GitHub
parent 4dc89df4a6
commit c49fa9415f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions

View File

@ -7,3 +7,8 @@ scipy>=1.0
# with modern importlib-metadata (4.8.1). importlib-metadata is only needed on
# Python <3.8.
importlib-metadata==4.6.4
# Jinja2 3.1.0 is incompatible with sphinx and/or jupyter until they are updated
# to work with the new jinja version (the jinja maintainers aren't going to
# fix things) pin to the previous working version.
jinja2==3.0.3