Skip to content

Commit

Permalink
setup: tighten version constraint on Jinja2.
Browse files Browse the repository at this point in the history
I remember thinking that not constraining it properly might bite us
someday, but assumed that Jinja2 will always stay version 2. Now it
looks like Jinja2 3.0.0a1 got released, pip picks it by default, and
it's currently broken (something about markupsafe missing).

Do what needed to be done in the first place.
  • Loading branch information
whitequark committed Apr 2, 2020
1 parent 2d1e12d commit 6e1145e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ def local_scheme(version):
install_requires=[
"setuptools",
"pyvcd~=0.1.4", # for nmigen.pysim
"Jinja2", # for nmigen.build
"Jinja2~=2.11", # for nmigen.build
],
packages=find_packages(),
entry_points={
Expand Down

0 comments on commit 6e1145e

Please sign in to comment.