[EPEL-devel] What is the proper way to handle python3 python36 in RHEL7

[Erinn Looney-Triggs]

I am trying to build a package for RHEL 7 and RHEL 8 that depends on an EPEL (for RHEL 7)
package python36-dbus the requires section goes like so:
Requires: %{python3}
Requires: %{python3}-dbus

This puts in a requirement for python3-dbus for RHEL 7 which doesn't exist, the
package is actually python36-dbus, however short of a conditional saying if rhel 7 then
package name is python36-dbus is there a clean and scalable way to make sure the package
version is correct?

I am looking into python3_pkgversion macro but that doesn't seem to be correct either.
Does anyone know how I should do this now with a single spec file for both RHEL 7 and 8
that doesn't contain a conditional expression? 

Thanks,
-Erinn