projects / nmigen.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 939d68e) | patch
setup: tighten version constraint on Jinja2.
authorwhitequark <whitequark@whitequark.org>
Thu, 2 Apr 2020 01:35:39 +0000 (01:35 +0000)
committerLuke Kenneth Casson Leighton <lkcl@lkcl.net>
Fri, 31 Dec 2021 13:21:43 +0000 (13:21 +0000)
commita268bb2dea96e409906c65b19b2cf22fef46462a
treeaf29ea0990bbf7ab4c42a730d3f0f9b4845e0ea8tree
parent939d68e77df7271655ac930af41eeb1bf8925d11commit | 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