Bug 1738159

Summary: tomoe depends on Python 2
Product: [Fedora] Fedora Reporter: Lumír Balhar <lbalhar>
Component: tomoeAssignee: Peng Wu <pwu>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: dingyichen, i18n-bugs, petersen, pnemade, pwu, tagoh, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tomoe-0.6.0-43.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-22 06:28:39 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-06 13:18:31 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 tomoe'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 tomoe.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

Comment 1 Peng Wu 2019-08-13 09:42:35 UTC
- What is the reason for the Python2 dependency?

It just provide Python bindings.

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

The upstream is not so active now.

- What is the guidance for porting to Python 3?

Maybe we disable the python binding for now, if no other package needs this binding.

Comment 2 Lumír Balhar 2019-08-13 11:22:12 UTC
It seems that only tomoe-gtk depends on tomoe. Tomoe-gtk should work without tomoe Python bindings but also has to be solved because it also depends on Python 2.

Comment 3 Ben Cotton 2019-08-13 16:48:55 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 4 Peng Wu 2019-08-15 03:17:58 UTC
Okay, I just updated tomoe without python binding.

Koji URL: https://koji.fedoraproject.org/koji/buildinfo?buildID=1354156

Comment 5 Lumír Balhar 2020-09-22 07:11:44 UTC
From the last build.log:

checking for python... no
checking for python2... no
checking for python3... /usr/bin/python3
checking for python version... 3.9
checking for python platform... linux

Good job!