Bug 1738123

Summary: pyside-tools depends on Python 2
Product: [Fedora] Fedora Reporter: Lumír Balhar <lbalhar>
Component: pyside-toolsAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: geertj, hobbes1069, jreznik, klember, mhroncok, rdieter, than
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-21 12:13: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:07:03 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 pyside-tools'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 pyside-tools.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

Comment 1 Ben Cotton 2019-08-13 16:56:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 2 Ben Cotton 2019-08-13 17:43:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 3 Lumír Balhar 2019-08-15 07:06:53 UTC
Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.

Comment 4 Lumír Balhar 2019-08-22 07:12:20 UTC
Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.

Comment 5 Lumír Balhar 2019-08-30 05:36:40 UTC
Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.

Comment 6 Richard Shaw 2019-09-06 17:33:22 UTC
Per the discussion on the devel list I am going to attempt to move the two consumers of Pyside1 over to Pyside2 (I'm already working on FreeCAD). Then we should be able to retire PySide1/Shiboken/apiextrator.

Comment 7 Miro Hrončok 2019-09-08 18:47:54 UTC
To clarify, this (pyside-tools) is the consumer of python2-pyside and you'll attempt to convert it to python3-pyside2, correct?

Comment 8 Richard Shaw 2019-09-08 21:52:39 UTC
(In reply to Miro Hrončok from comment #7)
> To clarify, this (pyside-tools) is the consumer of python2-pyside and you'll
> attempt to convert it to python3-pyside2, correct?

Yes, that's the hope.

Comment 9 Lumír Balhar 2019-09-16 18:45:11 UTC
Thanks for the info.

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, please orphan the package.

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 10 Richard Shaw 2019-10-13 12:13:46 UTC
I built freecad for Rawhide (f32) so it no longer depends on this package but I haven't built for f31/30 due to the requirement to do major package upgrades (separate issue).

I'm willing to build for f31/30 but was waiting on consensus from the devel list:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/RMWY7KZIPWNOYPZE7ZOHEZGCN334T2BW/

Comment 11 Richard Shaw 2019-10-17 15:44:56 UTC
FreeCAD has been built for PySide2 in f30/31.

Do we want to wait until it hits stable to retire the PySide1 stack?

Comment 12 Miro Hrončok 2019-10-17 18:38:37 UTC
We can wait a week...

Comment 13 Richard Shaw 2019-10-30 13:41:06 UTC
Everything is in stable (finally with the f31 launch).

Comment 14 Miro Hrončok 2019-11-21 12:13:50 UTC

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