Some users have requested that the client parts of Beaker support running in Python 3. Our client code is still targetting RHEL6+ (meaning Python 2.6+) but it would be reasonable to support Python 2.6+ and 3.0+ from a single code base, for the client parts. (The Beaker server side is another kettle of fish, it will be stuck on Python 2 so long as there is still TurboGears / CherryPy2 code. So that is out of scope for this bug.) Some outstanding issues: * need to fix syntax that is invalid in Python 3 * need to use six.moves for modules that changed names in Python 3 * need to get off python-krbV as it is unmaintained and there is no Python 3 port * need to figure out a testing strategy The latter point might be the hardest, as we are currently only running integration tests on RHEL6 and RHEL7. One easy option might be to get the tests running on Fedora, and then adjust the spec so that the beaker-client package on Fedora is built against Python 3 instead of Python 2.
Bug 1455425 is for switching python-krbV to something else with Python 3 support. But that is stalled due to deficiencies with krb5 on RHEL6 (details in that other bug). An alternative would be to port python-krbV to Python 3, but that seems like it might be a big thing to tackle.
Building in Rawhide is now blocked pending this, paricularly in the documentation subtree.
Yes, I'm aware of it. Getting there but we need to incorporate a bit more changes till 27.0
The build is available on Beaker-project website - https://beaker-project.org/nightlies/develop