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 gourmet'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 gourmet. If you need anything from us, or something is unclear, please mention it here. Thank you.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages If you need any information or help, or if you need some more time, please let us know.
Q: 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?) A: The software is written in python. Q: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?) A: See https://github.com/thinkle/gourmet/issues/696 & https://github.com/thinkle/gourmet/issues/697
> A: See https://github.com/thinkle/gourmet/issues/696 & https://github.com/thinkle/gourmet/issues/697 These seem somewhat stale, unfortunately. From a pull request from 2016 with many conflicts, it doesn't look like upstream is interested in patches. Do you think a python3 version can get into Fedora by November, or will gourmet need a FESCo exception to stay in Fedora 32?
You're right that upstream doesn't seem too interested in patches to port to python 3. I'm working to port this package myself, because I would like to see it remain in Fedora. Admittedly, I have 0 experience with porting programs from python 2 to 3, but there seems to be a lot of knowledge out there on the topic.
Here's one I helped with: https://portingguide.readthedocs.io/en/latest/ If there's something unclear or missing there, let me know. (Unfortunately I can't help port all the python2 packages, but I'll try to keep the guide useful.) gtk2 might still be a problem.
Also, please switch from python-beautifulsoap to python-beautifulsoap4 which has dual support for both Pythons.
Anything new here? Can I help you somehow?
*** This bug has been marked as a duplicate of bug 1777630 ***