RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

I would very much like to add python3-tomli to RHEL 9.

The currently shipped TOML-parsing module in python3-toml is deprecated in Fedora [1] and unwanted in RHEL 10 [2]. Projects that wish to support RHEL 9 as well as Fedora and RHEL 10+ need to maintain a complex spaghetti of ifs or try-excepts to choose their TOML-parsing module.

Some Red Hat upstream projects even justify reverting community contributions to migrate to a modern and upstream-maintained TOML parser by the absence of tomli in RHEL 9 [3]. We don't want that. We want all upstreams to be able to switch to tomllib on Python 3.11+ with a fallback to tomli. In order to make that easier for them, we should make tomli available in RHEL 9.

The package is already available in EPEL 9 [4] where I helped with the initial review and the EPEL maintainer is on board with us introducing this package to RHEL proper [5].


[1] https://fedoraproject.org/wiki/Changes/DeprecatePythonToml
[2] https://tiny.distro.builders/config-unwanted--sst_cs_apps-unwanted-python3-eln.html
[3] https://github.com/containers/podman-py/pull/240
[4] https://src.fedoraproject.org/rpms/python-tomli/tree/epel9
[5] https://github.com/containers/podman-py/pull/240#issuecomment-1440308239

Addition to the c9s workload: https://github.com/minimization/content-resolver-input/pull/784

Diff against EPEL 9: https://src.fedoraproject.org/rpms/python-tomli/pull-request/21

(In reply to Miro Hrončok from comment #5)
> Diff against EPEL 9:
> https://src.fedoraproject.org/rpms/python-tomli/pull-request/21

I wnt ahead and added a smoke test TMT plan to the PR as I anticipated it will be required.

With mock-core-configs at least 38.3-1.fc37 (currently a pending update):

$ mock -r centos-stream-9-x86_64 init
...
$ mock -r centos-stream-9-x86_64 --enablerepo=local install python3-tomli
...
Installed:
  python3-tomli-2.0.1-5.el9.noarch

$ repoquery -q --repo=c9s-appstream python3-tomli
python3-tomli-0:2.0.1-5.el9.noarch

$ repoquery -q --repo=RHEL9.3-AppStream python3-tomli
python3-tomli-0:2.0.1-5.el9.noarch

Yay \o/

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (python-tomli bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6325