In line with the Mass Python 2 Package Removal , the following (sub)packages of bodhi were marked for removal:
According to our query, those (sub)packages only provide a Python 2 importable module. If this is not true, please tell us why, so we can fix our query.
Please remove them from your package.
As said in the change document, if there is no objection in a week, we will remove the package(s) as soon as we get to it. This change might not match your packaging style, so we'd prefer if you did the change. If you need more time, please let us know here.
We hope this doesn't come to you as a surprise. If you want to know our motivation for this, please read the change document .
I would like more time to finish converting Bodhi's server code to Python 3. I expect the upcoming Bodhi 3.11.0 release to fully support Python 3 server side, and plan to release that before Fedora 30 branches (and likely long before that, possibly even in the next month or two). Is that acceptable?
Sure it is. getting somethign run on Python 3 is always better than ditching it.
This pull request switches bodhi-server to use Python 3 and drops a majority of Bodhi's Python 2 dependencies:
It seems that I still have one Python 2 dependent package though: fedora-easy-karma. It uses python2-bodhi-client, which uses python2-bodhi, so we aren't quite ready to drop those packages and their dependencies yet (so there are still a few Python 2 dependencies in Bodhi.
Shall we keep this ticket open until f-e-k is ready, or do you want to repurpose this ticket to track bodhi-server switching to Python 2 and open a new ticket with f-e-k is switched?
> This pull request switches bodhi-server to use Python 3 and drops a majority of Bodhi's Python 2 dependencies
> Shall we keep this ticket open until f-e-k is ready
We shall keep this ticket open until f-e-k is ready.
I'll also open a f-e-k bugzilla and make this one depend on it.
I'm preparing a PR.