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.
+1

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).

+1 to the exception

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

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

https://pagure.io/packaging-committee/pull-request/843 - merged

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.