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 bibus'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 bibus. If you need anything from us, or something is unclear, please mention it here. Thank you.
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.
I'm not the maintainer but I would've been interested in helping keeping bibus in Fedora for NeuroFedora. Unfortunately, it does not appear to be too active, and the work required to move it to python3 is quite a bit: https://sourceforge.net/p/bibus-biblio/discussion/380177/thread/d2dba9cc/ So it maybe worth orphaning it at the moment and re-adding it to Fedora if/when the port to python3 is complete. :/
The maintainer can, of course, orphan this package. Because it's a leaf package, it can be also retired directly.
According to the procedure described in https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages the package was now orphaned. If you think it was a mistake, you can provide the answers and claim the package back. Let us know if you need any help or just need more time.
Can somebody just retire this package? It would save me the step of filing a ticket to adopt it, then retire it. :-)
There is no other procedural way of retiring this than taking it I am afraid. Anyway, I suggest you just ignore this package when it comes to dropping wxPython or not.
This was retired.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days