Added specific version range for jinja2 #26
Merged
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.
Due to changes in the latest released jinja2 the project is failing to run.
The following exception is thrown:
Attaching to docker_bot_1
bot_1 | Traceback (most recent call last):
bot_1 | File "run_test.py", line 4, in
bot_1 | from youengine.helpers.analyze import analyze_mpl, analyze_bokeh
bot_1 | File "/opt/bot/youengine/helpers/analyze.py", line 4, in
bot_1 | import bokeh.plotting
bot_1 | File "/usr/local/lib/python3.8/site-packages/bokeh/plotting/init.py", line 67, in
bot_1 | from ..document import Document; Document
bot_1 | File "/usr/local/lib/python3.8/site-packages/bokeh/document/init.py", line 35, in
bot_1 | from .document import DEFAULT_TITLE ; DEFAULT_TITLE
bot_1 | File "/usr/local/lib/python3.8/site-packages/bokeh/document/document.py", line 49, in
bot_1 | from ..core.templates import FILE
bot_1 | File "/usr/local/lib/python3.8/site-packages/bokeh/core/templates.py", line 42, in
bot_1 | from jinja2 import Environment, FileSystemLoader, Markup
bot_1 | ImportError: cannot import name 'Markup' from 'jinja2' (/usr/local/lib/python3.8/site-packages/jinja2/init.py)
docker_bot_1 exited with code 1
By adding a specific version range in requirements.txt for jinja2, the issue is fixed.
Jinja2>=2.10.1,<3.1