From a268bb2dea96e409906c65b19b2cf22fef46462a Mon Sep 17 00:00:00 2001
From: whitequark <whitequark@whitequark.org>
Date: Thu, 2 Apr 2020 01:35:39 +0000
Subject: [PATCH] setup: tighten version constraint on Jinja2.

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 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/setup.py b/setup.py
index f80d30d..be6087a 100644
--- 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={
-- 
2.30.2