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 python2-django1.11'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 python2-django1.11. 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.
Hi, i don't think there is plan to move django1.11 to Python3 as there is already a Python3 version https://apps.fedoraproject.org/packages/python-django i see that 2 packages depend on it (if i'm not wrong): cobbler-web and fts-monitoring. The latter is mine, and i don't have plans to move it to Python3 now, so i will retire it from Rawhide. i will update the other ticket i also got (https://bugzilla.redhat.com/show_bug.cgi?id=1738006) What about cobbler-web? i guess there is a similar ticket open to that package as it depends on Python2. thanks cheers Andrea
Thanks for the info. (Yes, the questiong are very generic.) Cobbler 3 (with py3 support) is hopefully coming soon: https://bugzilla.redhat.com/show_bug.cgi?id=1737925 There is also python-oauth2client, but that fails to build: https://bugzilla.redhat.com/show_bug.cgi?id=1736516 If you're OK with this package getting removed when no longer required by other packages, there's nothing to do right now. We'll remove it when it's time. (Removing remaining Python 2 packages without an exception are scheduled for middle of November.)
ok, we can keep the package then until middle of November
Nothing depends on python2-django1.11 in Rawhide any more; it could be retired there. I don't know if I read your comment correctly. Do you need this packaged in Rawhide (f32) until November, or can we retire it there? In mid-November, we're planning to remove *all remaining py2 packages. The more there are, the more things might break. Removing python2-django1.11 from Rawhide *now* would make it possible to start removing things it depends on (like python-memcached, python-bcrypt, ...) more gradually, so we have a few more months to fix issues in case something goes wrong.
Let's just do it, I've opened bz1748071. *** This bug has been marked as a duplicate of bug 1748071 ***