Fixup: PR 811: install an upper-bounded version of Jinja2 during documentation build #812
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm hopeful that this will resolve the continuous integration failure in #811.
It looks like the
ImportError: cannot import name 'environmentfilter' from 'jinja2'
error seen in the build logs there is a symptom of using some less-recent versions ofsphinx
(as packaged with stable/LTS Ubuntu versions) with quite-recent versions ofJinja2
-- particularly v3.1.0 ofJinja2
and beyond.Until a recent-enough version of
sphinx
is available in theubuntu-latest
GitHub runner image, it should be possible to install an upper-bounded version ofJinja2
as a workaround.Ref: Jinja 2 imports have been deprecated sphinx-doc/sphinx#10291
Ref: 3.1.0 update breaks Sphinx 3.5 pallets/jinja#1630
(please note: this pull request is opened against the master branch instead of the #811 pull request branch so that it is eligible for continuous integration -- but it's intended to be merged into #811)