https://bugzilla.redhat.com/show_bug.cgi?id=1772578
--- Comment #13 from Miro Hrončok mhroncok@redhat.com --- (In reply to Cristian Le from comment #12)
But what about any fixes/changes that are introduced in importlib_resources>=6.0 which correspond to Python3.13 [1], for example [2]. What I'm trying to say is that this package should not be treated any differently from `importlib_metadata` or `typing_extensions`.
I see. You explicitly mentioned Python<3.12.
I guess it's unavoidable to introduce it if upstreams depend on it :/
Regarding Python<3.12, this is still needed for EPEL9.
Yeah, for EPEL, it makes perfect sense.