#2031 Allow python-readme render to add python2-readme-renderer to Fedora 28 and 29
Closed: Accepted 7 months ago Opened 8 months ago by bowlofeggs.

Greetings fellow FESCo dudes!

I have been working on updating python-twine to 1.12.2. Unfortunately, it introduced a new dependency on python-readme-renderer.

The Python packaging guidelines say that "Software using python2 MUST NOT be newly packaged without FESCo exception." For Rawhide this was fine, because python-twine is Python 3 only there. However, for Fedora 28 and 29, python-twine has subpackages for both Python 2 and 3.

I would like an exception to add python2- subpackage to python-readme-renderer for Fedora 28 and 29 so that I can update Twine there, because there is a report that our version of twine doesn't work with PyPA and I am hoping that the latest version of Twine will fix that.

Not sure if the guidelines apply since it is not new software, i.e. a new package review. Nevertheless, adding the new python2 subpackage only to Fedora 28/29 seems like a good approach here.

Well it was new software just last week when I added it to Fedora. At the time, I hadn't realized that I would hit this problem.

Should we change the wording on that guideline to specify that new Python 2 software should not be added to Rawhide, or do we want people to ask for exceptions for stable releases like I am doing?

+1 for the exception

I agree the wording should be changed. This shouldn't mention "rawhide" though, but instead "F30 and later".

On Thu, 2018-12-20 at 21:49 +0000, Zbigniew J=C4=99drzejewski-Szmek wrote:

This shouldn't mention "rawhide" though, but instead "F30 and later".

Well couldn't we end up in the same situation? Not all Python 2
packages are going to make it by Fedora 30 I assume.

Not all python2 will be removed in F30, or even for a long time, but I still think we should not allow new stuff to be added (the exception process would be appropriate for such cases).

The guidelines (written by me) are meant for Fedora 30+.

I'll submit a PR for the guidelines to make this more clear.

The FPC guidelines have been modified, and adding python2 packages to F28 or F29 does not need an exception anymore. This ticket is moot, let's close it.

Metadata Update from @zbyszek:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

7 months ago

Login to comment on this ticket.