jinja2 to jinja3 transition

[shreyb]

The current major version of jinja is jinja3. Currently, we use jinja2 because its RPM is available on EPEL. Once jinja3 is available, we'll want to be ready to transition our templating to jinja3 templates.

[marcmengel]

First stab at this looks not promising, to wit, from the ChangeLog:

Version 3.1.0
Released 2022-03-24

Drop support for Python 3.6. #1534

So moving up to jinja3 will involve changing away from using the system Python on both
SL7 and Centos8 (which also ships with /usr/bin/python3 version 3.6.8).

So we might want to reconsider...

[shreyb]

Oh - for sure. We don't want to do this right now. We could bundle our own python in the RPM in the future, or otherwise wait for CentOS 9 and see what that landscape looks like.

Should we keep this open for "some future date", or close this for now?

[marcmengel]

If we can mark it for "Future",. I think we should keep it -- I mean, we could rely on a newer devtools python and still do an RPM...

[shreyb]

Done.

[shreyb]

We'll need to handle this sometime in the next few months - experiments are already starting to move to EL8 and looking to EL9.