Bug 1739514

Summary:	skf depends on Python 2
Product:	[Fedora] Fedora	Reporter:	Lumír Balhar <lbalhar>
Component:	skf	Assignee:	Mamoru TASAKA <mtasaka>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	mtasaka
Target Milestone:	---	Keywords:	Triaged
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-11-05 04:33:05 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-09 13:39:56 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 skf'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 skf.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

Comment 1 Ben Cotton 2019-08-13 17:02:50 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 2 Ben Cotton 2019-08-13 17:18:53 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 3 Lumír Balhar 2019-08-19 10:38:18 UTC

Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.

Comment 4 Mamoru TASAKA 2019-08-19 12:05:45 UTC

Please do understand that replying to more than 10 bugs with multiple questions in 2 weeks (3 comments means 2 weeks) is really hard for volunteers, thank you.

Comment 5 Mamoru TASAKA 2019-08-19 12:22:04 UTC

There is already python3 binding, however currently I don't know how to use it, contacting upstream

Comment 6 Lumír Balhar 2019-08-26 13:30:01 UTC

Thank you for the info.

It seems that the Python bindings are generated by SWIG so it might be possible to switch it to Python 3.

Let me know if you need any help.

Comment 7 Lumír Balhar 2019-09-03 09:34:37 UTC

Is there any issue we can follow?

Comment 8 Mamoru TASAKA 2019-09-08 10:32:39 UTC

While you may want me to do python stuff first, please understand that I have other lots of things to do and I can just look at one by one. Also please know that I've already imported some packages written in python2 to python3. Again I can do just one by one. Now I am doing ruby stuff first.

Again I can do just one by one.

Comment 9 Mamoru TASAKA 2019-09-09 10:45:56 UTC

Once again, while I am going to work on this, I can do only one by one.

Comment 10 Mamoru TASAKA 2019-09-10 08:24:56 UTC

- The dependency for python2 is python2 bindings for skf
- The upstream is active
- There is already python3 bindings
- The problem is that I don't know how to use python3 bindings - because skf (Simple "Kanji" Filter) is a tool for converting "non-utf8" string to another "non-utf8" (or utf-8) string, and as python3 changed string <-> binary handling heavily, simply compiling swig-generated python3 binding is not enough - I must find out how to use it
- But again dependency for python2 is python2 bindings for skf, and importance is rather low

Comment 11 Lumír Balhar 2019-09-10 10:03:50 UTC

Thank you!

Comment 12 Mamoru TASAKA 2019-11-05 04:33:05 UTC

skf-2.10.11-1.fc32 dropped python2 support.