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 python-gunicorn'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 python-gunicorn.
If you need anything from us, or something is unclear, please mention it here.
Hmm. I think python-gunicorn might have been wrongly classified somehow. It seems like this bug is filed assuming gunicorn is Python-2-only but in fact it works on both Python 2 and 3, has been shipping a Python 3 subpackage for a long time. We would just drop the python2-gunicorn subpackage when Python 2 is retired.
Anyway, since gunicorn is apparently a leaf package, to make things simpler I will just drop the python2-gunicorn subpackage in F31+.
Perfect, thank you!