Bug 1738149

Summary:	vegastrike-data depends on Python 2
Product:	[Fedora] Fedora	Reporter:	Lumír Balhar <lbalhar>
Component:	vegastrike-data	Assignee:	Hans de Goede <hdegoede>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	bruno, 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-10 15:39:50 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:17:37 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 vegastrike-data'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 vegastrike-data.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

Comment 1 Hans de Goede 2019-08-07 09:17:38 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?) 

vegastrike is a game which embeds the python2 interpreter, all of the "levels" and much of the game logic is implemented as python2 classes which are shipped as part of the -data package.

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

Vegastrike has been in a zombie state upstream for a long time now. There is a python3 branch, which was intended to lead to a new release, but that has not been touched for years and no new release has happened. We could move to the unstable python3 branch, but I believe that it is better to just retire vegastrike.

Therefor I plan to retire vegastrike for F31+

Comment 2 Hans de Goede 2019-08-10 15:39:50 UTC

Vegastrike upstream is in zombie state, there is an old unstable python 3 branch but that never got finished / stabilized. Since there is no viable python3 version, vegastrike has been retired.