setup: tighten version constraint on Jinja2.
authorwhitequark <whitequark@whitequark.org>
Thu, 2 Apr 2020 01:35:39 +0000 (01:35 +0000)
committerwhitequark <whitequark@whitequark.org>
Thu, 2 Apr 2020 01:35:39 +0000 (01:35 +0000)
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.

setup.py

index f80d30d66cec4f7a52c949373b27284b592d3836..be6087aa02db93120d5b522c1332bd117955f015 100644 (file)
--- a/setup.py
+++ b/setup.py
@@ -27,7 +27,7 @@ setup(
     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={