Here we are tracking bugs where the package already contains a Python 3 subpackage, but the subpackage has a dependency on Python 2 as well. This is a problem, because it basically renders the porting effort useless. There is a section [0] of the Python RPM Porting Guide dedicated to this problem to aid maintainers in solving it. [0] http://python-rpm-porting.readthedocs.io/en/latest/application-modules.html#are-shebangs-dragging-you-down-to-python-2
We don't need this tracker any more, the number of these packages is low enough.