Bug 1738168

Summary:	swift-lang depends on Python 2
Product:	[Fedora] Fedora	Reporter:	Lumír Balhar <lbalhar>
Component:	swift-lang	Assignee:	Ron Olson <tachoknight>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	tachoknight
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-14 06:04:00 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:20:11 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 swift-lang'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 swift-lang.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

Comment 1 Ron Olson 2019-08-07 02:01:18 UTC

- 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?) 

Answer: Apple used Python2 for their custom build scripts

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

Answer: Unknown, as macOS still uses Python2 and will at least for the next year (will be looking to see what happens with the next version, but that won't be revealed until June, 2020)

- 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?)

Answer: Patches have already been applied to make Swift build entirely using Python 3. These patches have been made available to Apple (https://github.com/apple/swift/pull/26296) and until they or something equivalent is merged, the spec file applies the patches itself. 

As of Swift 5.1, Python 2 is no longer a dependency; I am waiting for the official release of 5.1 and until then will be occasionally updating Rawhide to make sure all is working fine. After 5.1 is released I will not be updating the 5.0.x versions.

Comment 2 Ben Cotton 2019-08-13 17:00:21 UTC

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

Comment 3 Ben Cotton 2019-08-13 17:35:20 UTC

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

Comment 4 Lumír Balhar 2019-08-14 06:04:00 UTC

I can confirm that this package does not depend on Python 2 in rawhide.