Bug 1738970

Summary: gcompris depends on Python 2
Product: [Fedora] Fedora Reporter: Lumír Balhar <lbalhar>
Component: gcomprisAssignee: Hans de Goede <hdegoede>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: fedora, gwync, hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-10 15:42:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1698500    

Description Lumír Balhar 2019-08-08 12:08:20 UTC
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 gcompris'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 gcompris.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

Comment 1 Hans de Goede 2019-08-08 12:25:03 UTC
(In reply to Lumír Balhar from comment #0)
> - 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?) 

gcompris is a mixed C-code / python app with most of its educational "activities" implemented in python.

> - What are the upstream/community plans/timelines regarding Python 3?

The original gcompris, aka "gcompris" in Fedora is no longer maintained upstream, upstream has rewritten gcompris in QT, gcompris-qt in Fedora and has been porting all the activities from gcompris to gcompris-qt one at a time. We've been keeping the original gcompris around since not all activities have been ported yet.

Given that most activities have been ported by now and upstream has no plans to support python3 in the original gcompris, I believe the best thing to do is to retire the original gcompris package.

When I have some time I will retire gcompris and then close this bug.

Comment 2 Hans de Goede 2019-08-10 15:42:37 UTC
I've just retired gcompris, closing.