Bug 1731626

Summary:	glue-validator depends on Python 2
Product:	[Fedora] Fedora	Reporter:	Lumír Balhar <lbalhar>
Component:	glue-validator	Assignee:	Laurence Field <Laurence.Field>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	Laurence.Field, mhroncok
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-28 01:13:33 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-07-20 06:32:34 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 glue-validator'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?) [remove if clear]

- 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 glue-validator.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

Comment 1 Lumír Balhar 2019-07-20 06:33:08 UTC

By the way, the upstream URL http://cern.ch/glue does not work (Err 404).

Comment 2 Laurence Field 2019-07-23 09:49:29 UTC

This code is no longer under active development but is still useful. The code now resides in git hub (https://github.com/EGI-Foundation/glue-validator/). It should be straight forward to port to python3 and this can be done if need.

Comment 3 Lumír Balhar 2019-07-29 04:54:10 UTC

Upstream question: https://github.com/EGI-Foundation/glue-validator/issues/2

Do you plan to port it to Python 3?

Comment 4 Lumír Balhar 2019-08-05 08:49:48 UTC

Unfortunately, it seems, that the upstream developer has no intention to port glue-validator to Python 3 [0]. Do you have a plan to port it or do you know somebody who plans to do it?

[0] https://github.com/EGI-Foundation/glue-validator/issues/2#issuecomment-516472323

Comment 5 Ben Cotton 2019-08-13 18:33:57 UTC

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

Comment 6 Lumír Balhar 2019-08-14 08:48:39 UTC

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 7 Miro Hrončok 2019-11-28 01:13:33 UTC


*** This bug has been marked as a duplicate of bug 1777629 ***