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.
This commit is contained in:
parent
2d1e12d00c
commit
6e1145e2e7
Loading…
Reference in a new issue