projects / nmigen.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 2d1e12d) | patch
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)
commit6e1145e2e7be13f3d5037881380b3752d5590785
treeaf29ea0990bbf7ab4c42a730d3f0f9b4845e0ea8tree
parent2d1e12d00ca13ce6ad92fe145beeaa74925de6efcommit | diff
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 diff | blob | history