Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
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.
- Loading branch information