Bug 1738013

Summary: lizardfs depends on Python 2
Product: [Fedora] Fedora Reporter: Lumír Balhar <lbalhar>
Component: lizardfsAssignee: Jonathan Dieter <jonathan>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: jonathan, pviktori
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-08-24 16:07:53 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:31:02 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 lizardfs'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 lizardfs.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

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

Comment 2 Lumír Balhar 2019-08-14 09:08:38 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, please let us know.

Comment 3 Jonathan Dieter 2019-08-14 09:13:20 UTC
I'm sorry, but threatening to orphan the package a week after opening the bug report is a bit antisocial. I need to take a look at this because I don't actually know the answers yet, but it will probably be a few weeks before I have the spare cycles to deal with it.

Comment 4 Lumír Balhar 2019-08-14 09:34:24 UTC
I understand you completely but we also need to gather some responses for all components and we have hundreds of bugs without any. We don't orphan the component immediately (see the nonresponsive policy in the change description).

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, and nothing in Fedora uses it, you can retire it or just remove the Python 2 part from it (subpackage, module, bindings, etc.).

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

Comment 5 Jonathan Dieter 2019-08-14 09:48:08 UTC
I understand, but you're putting pressure on me to look at this now, and, being quite frank, this shouldn't be urgent. I wasn't even aware that lizardfs had a python dependency, given that it's a fuse filesystem mainly written in C++. 

I'm currently getting on a flight to be with my family for a funeral, so I am not going to look at this until next week at the earliest.

Again, while I understand (and commend) your desire to retire python 2, it shouldn't translate into urgent work for everybody else. Just because it's in the change description doesn't mean it's the right way to treat our packagers.

Comment 6 Petr Viktorin (pviktori) 2019-08-14 10:28:35 UTC
Hello,
This is not urgent. You have time until November.

Thank you for responding. There are hundreds of bugs where the packager doesn't respond, and is then surprised when a package is removed or has missing dependencies. We want to give out the warning early.
Sorry for wording it too harshly. It's difficult to find wording that works for everyone.

We'll try to not to nag you about lizardfs until November. (But that also means you won't get any more warnings, unless you ask.)

If you need more time than that, let us know.

Comment 7 Jonathan Dieter 2019-08-24 16:07:53 UTC
Ok, I've investigated and it turns out the cgi servers are written in Python 2.  Converting them to Python 3 was pretty simple, so I've gone ahead and done so, and pushed the update to Rawhide.  Good luck on the Python 2 retirement!

https://koji.fedoraproject.org/koji/taskinfo?taskID=37256602