Bug 1884798

Summary: swift-lang requires Python 2 to build
Product: [Fedora] Fedora Reporter: Petr Viktorin (pviktori) <pviktori>
Component: swift-langAssignee: Ron Olson <tachoknight>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: 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: 2022-06-08 00:56:18 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: 1803205    
Bug Blocks:    

Description Petr Viktorin (pviktori) 2020-10-02 19:55:10 UTC
Python 2 reached upstream end-of-life in January 2020. In Fedora, it's now provided from the deprecated compat package `python27`. It should not be added as a new  dependency, as it was in swift-lang 5.3-1.

If it's possible that the dependency won't be removed in Fedora 34, please request a FESCo exception. You can refer to the exception for mercurial as an example: https://pagure.io/fesco/issue/2243
It's good to mention:

- What is the reason for the Python 2 build dependency?

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

- What is the guidance for porting the build 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?)

If you need anything from us, or something is unclear, please mention it here.

Comment 1 Ron Olson 2020-10-02 20:25:38 UTC
Hi-

I am very aware of Fedora's desire to sunset Python 2, and commented on this very issue on the Swift forums: https://forums.swift.org/t/python-3-support-for-building-swift-toolchain/27020. The Swift folks have been actively working towards removing Python 2 as a dependency (for example: https://github.com/apple/swift/pull/32685) but this was not done in time for Swift 5.3 as the code is frozen presumably per an internal schedule probably related to the next version of iOS, macOS, etc. 

The Python 2 dependency is there because the Swift toolchain uses it for building.

I do not know what version will be declared Python 2-free (next-version builds have not yet been made available per https://github.com/apple/swift/releases/) and the main branch (that the next version will be forked from) does not yet consistently build cleanly because of the number and variety of commits that is normal for a large, active project.

Comment 2 Petr Viktorin (pviktori) 2020-10-02 20:40:58 UTC
Thanks for the info! Glad to hear this is moving forward.

Comment 3 Ben Cotton 2021-02-09 15:19:39 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 4 Ben Cotton 2022-05-12 16:36:39 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Ben Cotton 2022-06-08 00:56:18 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.