Bug 1731402 - driconf depends on Python 2
Summary: driconf depends on Python 2
Alias: None
Product: Fedora
Classification: Fedora
Component: driconf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F31_PY2REMOVAL
TreeView+ depends on / blocked
Reported: 2019-07-19 10:36 UTC by Lumír Balhar
Modified: 2019-07-22 09:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-07-22 09:20:07 UTC
Type: Bug

Attachments (Terms of Use)

Description Lumír Balhar 2019-07-19 10:36:19 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 driconf's future. Specifically:

- 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 driconf.
If you need anything from us, or something is unclear, please mention it here.

Thank you.

Comment 1 Lumír Balhar 2019-07-19 10:36:47 UTC
The last release is from 2013 so I am not sure how much active this project is.

Comment 2 Kevin Fenzi 2019-07-20 19:05:20 UTC
Yep. I am fine retiring this package. There is now adriconf which has a lot more settings, supports gtk3/wayland, etc... 

Just let me know when or feel free to retire it yourself.

Comment 3 Miro Hrončok 2019-07-22 09:20:07 UTC
Retired. Thanks.

Note You need to log in before you can comment on or make changes to this bug.