Bug 2153843

Summary:	[REBASE: RHEL9] jinja2 to 3.1 or higher
Product:	Red Hat Enterprise Linux 9	Reporter:	Pat Riehecky <riehecky>
Component:	python-jinja2	Assignee:	Python Maintainers <python-maint>
Status:	CLOSED WONTFIX	QA Contact:	RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, jwboyer, pviktori
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-25 13:19:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pat Riehecky 2022-12-15 16:01:48 UTC

Description of problem:
There are some new features of jinja that I'd love to use in RHEL9.  Can the package be rebased to version 3.1 or higher?

Version-Release number of selected component (if applicable):
2.11.3-4.el9

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Petr Viktorin (pviktori) 2023-01-11 13:14:24 UTC

There were breaking changes, so we can't simply rebase. Is there a particular feature you need backported?
To help prioritization, could you submit a customer case with business justification?

Comment 2 Pat Riehecky 2023-01-11 15:32:08 UTC

The biggest driver in my case is python-pandas which has shifted to the jinja 3 code base.

Comment 3 Petr Viktorin (pviktori) 2023-01-25 13:19:34 UTC

Without a business justification, we unfortunately cannot upgrade jinja in RHEL9 and risk breakage.

I see you're packaging pandas into EPEL, let's discuss the options there: https://bugzilla.redhat.com/show_bug.cgi?id=2032550