Please branch and build python-jinja2 in epel9. If you do not wish to maintain python-jinja2 in epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/python-jinja2/addgroup and grant it commit access, or collaborator access on epel* branches. I would also be happy to be a co-maintainer (FAS: jonathanspw). I can be the primary contact for EPEL (FAS: jonathanspw).
There already exists a python3-jinja2 package in appstream 9.x/9s, so we can't simply branch and build. This is version 2.11.3, though. So, as the request really is about >=3, we'd need to make an EPEL9-only package python3-jinja2-31 or similar, I guess. Will have a look how that works nowadays.
> we'd need to make an EPEL9-only package python3-jinja2-31 or similar, I guess. Will have a look how that works nowadays. Note that the package would conflict (on files level) with python3-jinja and conflicts with RHEL are not allowed in EPEL unfortunately.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
There isn't really a feasible solution for this. The real answer will be dropping the pandas version being packaged for EPEL 9 to a version that is compatible with the version of jinja2 that in RHEL 9 AppStream.