Bug 1737956

Summary: edk2 depends on Python 2
Product: [Fedora] Fedora Reporter: Lumír Balhar <lbalhar>
Component: edk2Assignee: Paolo Bonzini <pbonzini>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: berrange, crobinso, kraxel, pbonzini, philmd, virt-maint
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-07 08:20:48 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:06:44 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 edk2'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 edk2.
If you need anything from us, or something is unclear, please mention it here.

Thank you.
Comment 1 Cole Robinson 2019-08-06 17:38:05 UTC 
The latest f31 build doesn't seem to have a python2 dep:

[:~] $ ls edk2-*
edk2-aarch64-20190501stable-3.fc31.noarch.rpm    edk2-qosb-20190501stable-3.fc31.noarch.rpm
edk2-arm-20190501stable-3.fc31.noarch.rpm        edk2-tools-20190501stable-3.fc31.x86_64.rpm
edk2-ovmf-20190501stable-3.fc31.noarch.rpm       edk2-tools-doc-20190501stable-3.fc31.noarch.rpm
edk2-ovmf-ia32-20190501stable-3.fc31.noarch.rpm  edk2-tools-python-20190501stable-3.fc31.noarch.rpm
[:~] $ rpm -qp --requires edk2-* | grep python
/usr/bin/python3
python3
python3

Is there more info on how the python2 dep was determined?
Comment 2 Lumír Balhar 2019-08-07 08:20:48 UTC 
You are right. Info about edk2 was outdated in portingdb [0].

Thank you.

[0] https://fedora.portingdb.xyz/pkg/edk2/