Bug 1738044

Summary:	pyfribidi depends on Python 2
Product:	[Fedora] Fedora	Reporter:	Lumír Balhar <lbalhar>
Component:	pyfribidi	Assignee:	Hans de Goede <hdegoede>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	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-07 13:23:42 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 12:42:58 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 pyfribidi'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 pyfribidi.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

Comment 1 Gwyn Ciesla 2019-08-06 18:56:48 UTC

Required by childsplay.

Comment 2 Hans de Goede 2019-08-06 20:23:15 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?) 

pyfribidi is a python wrapper for the libfribidi C-library.

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

It looks like there is a new upstream here:
https://github.com/pediapress/pyfribidi

Which does have python 3 support. But the only reason have pyfribidi support in Fedora is childsplay which is largish an app written in python2 with no signs that its upstream is moving to python 3.

So I will likely retire both childsplay and pyfribidi for F31+ soon.

Comment 3 Hans de Goede 2019-08-07 08:47:37 UTC

Gwyn, sorry I missed your earlier response somehow.

As mentioned it does not look like childsplay upstream has any plans to port it to pythoin3, so I believe it is best to retire both childsplay and pyfribidi. Do you agree, or do you have some plan to move childsplay over to python3 ?

Comment 4 Gwyn Ciesla 2019-08-07 13:17:13 UTC

No, I concur, they can both be retired. I can do it, unless you'd rather.

Comment 5 Hans de Goede 2019-08-07 13:18:53 UTC

(In reply to Gwyn Ciesla from comment #4)
> No, I concur, they can both be retired. I can do it, unless you'd rather.

If you can take care of retiring them both, then that would be great. Thank you.

Comment 6 Gwyn Ciesla 2019-08-07 13:23:42 UTC

Done.