|Summary:||gimp-layer-via-copy-cut depends on Python 2|
|Product:||[Fedora] Fedora||Reporter:||Lumír Balhar <lbalhar>|
|Component:||gimp-layer-via-copy-cut||Assignee:||Luya Tshimbalanga <luya_tfz>|
|Status:||ASSIGNED ---||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||rawhide||CC:||design-devel, eber67, fedora, luya_tfz, pviktori|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||1737933|
Description Lumír Balhar 2019-08-08 12:07:58 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 gimp-layer-via-copy-cut'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 gimp-layer-via-copy-cut. If you need anything from us, or something is unclear, please mention it here. Thank you.
Comment 1 Ben Cotton 2019-08-13 17:03:01 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:29:04 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-16 09:04:29 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 Luya Tshimbalanga 2019-08-16 15:20:22 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?) > The plugin is written in Python 2. > - What are the upstream/community plans/timelines regarding Python 3? > Upstream currently has no exact plan for porting to 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?) > It would be best to port to Python 3 using 2to3 script and send the fix to upstream https://www.deviantart.com/slybug/art/Layer-via-Copy-Cut-305728401
Comment 5 Petr Viktorin 2019-08-19 14:57:19 UTC
It only makes sense to do this after Gimp switches to Python 3. I expect there will be a FESCo exception to Gimp on Python 2, and it would make sense if the exception covers the plugin as well.
Comment 6 Ben Cotton 2020-11-03 15:30:46 UTC
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 7 Luya Tshimbalanga 2020-11-04 03:16:45 UTC
Changed to Rawhide.