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 sugar'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 sugar. If you need anything from us, or something is unclear, please mention it here. Thank you.
I sit on the Oversight Board for Sugar Labs, as an elected member. Sugar is written in Python, and it makes use of several components/python modules which were never ported to Python 3, such as Telepathy. Sugar was originally written in an era when Python 3 did not exist. We are aware of this impending deadline, and have been working to make our codebase compatible with Python 3. Python has no full time programmers, so testing is slow, but work is being done.
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.
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, please orphan the package. 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
going to use this as a tracker for sugar UX migration to python3 and link all the other bugs to depend on this so it can be tracked here.
I'm sorry for the spam! We're trying to gather the information on about 1000 packages. We forgot to check that these 80 of them are related, and just need to be asked once :( We've made a special case for "sugar-*" and "olpc-*" packages. Others (like "hippo-canvas") aren't that easy to catch: if you get more spam, please complain so we can fix it!
We're looking to deprecate hippo-canvas, it was used in the old gtk2 Activities, there's a few more to migrate to the gtk3. There's overall been a multi year effort to move to python3 including moving from gstreamer 0.10 python bindings to py3 friendly introspection based gst 1.0 bindings etc. There's only a handful of gtk2 based Activities left (repoquery --whatrequires sugar-toolkit)
Created attachment 1608780 [details] install sugar-desktop to Fedora-Mate-armhfp-31-20190824.n.0-sda.raw.xz branched f31 arm
> We are aware of this impending deadline I don't like to spam again, but the upstream deadline is in less than 3 months and the Fedora deadline is in little more than a month. I haven't seen much activity on the Fedora side, which makes me worry. Is everything on track? Do you need help getting an exception to keep Sugar on Python 2 in Fedora 32, to get some more time? As it is, the maintainers of packages like python2-numpy, python2-pygame, python2-pytest, python2-simplejson etc. are most likely preparing to remove them. Should we prepare to keep them instead?
Is everything on track for the mid-November deadline? Do you need any help?
Half a month until the deadline. Do you need more time? (If you do, let's get an exception soon!) Is there somewhere progress can be tracked? Are there issues upstream, or in packaging?
The Sugar code base and most activities have now been ported to Python 3, and Sugar 0.116 (unstable release) was made back on September 4th[1]. We should probably get a stable release made between now and then, and then this needs to be packaged for Fedora, along with the new Sugar activities, all of which also needed to be ported to Sugar 0.116/Python 3. [1] http://lists.sugarlabs.org/archive/sugar-devel/2019-September/057175.html
> We should probably get a stable release made between now and then Which "then" is that? It looks like Sugar won't make the November 15th deadline, and thus needs an exception. Is that right? If so, we need to coordinate with maintainers of Sugar's dependencies, so they don't remove Python 2 support on November 15. There's about a week to do that. Is that what we need to do?
FESCo ticket filed here: https://pagure.io/fesco/issue/2267
sugar-toolkit depends on python2-simplejson and that went away already. This is prevent SoaS images building in Rawhide, e.g. https://koji.fedoraproject.org/koji/taskinfo?taskID=39373467 .
Core Sugar shell/UX moved to py3.
Can this be closed as Peter pointed out, Sugar has moved to python3.
(In reply to Ibiam from comment #17) > Can this be closed as Peter pointed out, Sugar has moved to python3. We're using this one to track all of the sugar changes. You can see details here: https://bugzilla.redhat.com/buglist.cgi?bug_id=1737929&bug_id_type=anddependson&format=tvp&list_id=10855354
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This is being actively worked on and won't be magically fixed by F31 going EOL. Bumping.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.