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 nwchem'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 nwchem.
If you need anything from us, or something is unclear, please mention it here.
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, please let us know.
I believe upstream nwchem supports Python3, but nwchem Makefile settings are not flexible enough to support the way Python3 is packaged across various directories on Fedora.
Issue submitted upstream https://github.com/nwchemgit/nwchem/issues/136
Thank you. Let's wait for a while.
mpich-3.3.1 is in a buildroot override in F31. So if this bug depends on that in any way,
it is OK to proceed.
I can confirm that this package does not depend on Python 2 in rawhide.