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 votca-csg'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 votca-csg. 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.
Just a couple of scripts, upstream moved to python3 already, so the next version won't require python2, patch could be back-ported easily.
Perfect. Is there any plan for a new release or do you want to backport the upstream patch?
(In reply to Lumír Balhar from comment #7) > Perfect. Is there any plan for a new release or do you want to backport the > upstream patch? The release will happen in the next couple of months.
If we need to backport: https://github.com/votca/csg/pull/348
Thanks for the info. It might be necessary to backport the patches before a new release happens because we have a strict schedule. 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
FEDORA-2019-1504819f22 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1504819f22
votca-csg-1.5.1-1.fc31, votca-tools-1.5.1-2.fc31, votca-xtp-1.5.1-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-1504819f22
votca-csg-1.5.1-1.fc31, votca-tools-1.5.1-2.fc31, votca-xtp-1.5.1-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
votca-csg-common-1.5.1-1.fc32 still requires python 2.
*** Bug 1777614 has been marked as a duplicate of this bug. ***
*** Bug 1777613 has been marked as a duplicate of this bug. ***
Votca-1.6_rc1, which uses python3 exclusively should be out by the end of week.
Thank you!
Votca-*-1.6_rc1 is now in Rawhide and should only use python3.