Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for freeorion's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) This bug is filed semi-automatically, and might not have all the context specific to freeorion. If you need anything from us, or something is unclear, please mention it here. Thank you.
FreeOrion uses Python for AI scripting. It currently supports Python 2.7. I am investigating with the upstream community how (if at all) this can be migrated to Python 3.
Upstream community is already working towards migrating to Python 3.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
The current plan is to remove packages with dependency on Python 2 from Fedora 32 in the middle of November 2019. If you want to keep your package in Fedora after that date and you cannot port it to Python 3 yet, you need to request a FESCo exception for the package and all its Python 2 dependencies (even transitive) [1]. If you don't want to maintain it anymore, and nothing in Fedora uses it, you can retire it or just remove the Python 2 part from it (subpackage, module, bindings, etc.). If you're considering filing the exception request, let us know. We can help (for example, we can help find all the dependencies). [1] https://fedoraproject.org/wiki/Changes/RetirePython2#FESCo_exceptions
How far is the Python 3 support? Could you link to any discussion on this? Can this be done by mid-November, or does freeorion need an exception to keep using Python 2 a bit longer?
The boost maintainer would be very happy to drop Python 2 support: supporting a dual py2/py3 build is "a nightmare". But it is technically possible to keep boost-python2. Is it worth keeping python2-boost for freeorion and k3d?
Here is a PR for using `boost169`, which will retain Python 2 support: https://src.fedoraproject.org/rpms/freeorion/pull-request/1 See discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1767503
FYI I'm working patching freeorion for Python 3.
I've merged the PR to switch rawhide builds to using boost169. Note that this does not remove FreeOrion's runtime dependency on python2, but it does free up boost to drop Python 2 support. FreeOrion's upstream is actively working on converting their runtime code to Python 3[1]. https://github.com/freeorion/freeorion/pull/2653
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
*** This bug has been marked as a duplicate of bug 1881183 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days