Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1739552 - cfv depends on Python 2
Summary: cfv depends on Python 2
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: cfv
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F31_PY2REMOVAL
TreeView+ depends on / blocked
 
Reported: 2019-08-09 13:48 UTC by Lumír Balhar
Modified: 2020-10-02 20:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-02 20:11:16 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Lumír Balhar 2019-08-09 13:48:46 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 cfv'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 cfv.
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:58 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:15:15 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-19 11:28:03 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 manuel wolfshant 2019-08-19 11:35:51 UTC 
From my point of view the package can be orphaned and / or deprecated. I have no real interest in it, I do not know if anyone is using it and for reasons I have yet to identify I cannot obtain a valid Kerberos ticket to perform any operation on it  myself.

manuel
Comment 5 Lumír Balhar 2019-08-19 11:45:02 UTC 
cfv is a leaf package so it can be retired in Fedora rawhide.
Comment 6 Lumír Balhar 2019-08-26 13:52:42 UTC 
Miro, could you please orphan this package?
Comment 7 Miro Hrončok 2019-08-26 14:07:31 UTC 
Why don't we retire it right away if it is a leaf?
Comment 8 Lumír Balhar 2019-08-26 14:10:31 UTC 
(In reply to Miro Hrončok from comment #7)
> Why don't we retire it right away if it is a leaf?

Somebody might be interested in this package. And it will be retired automatically after a few weeks.
Comment 9 Miro Hrončok 2019-08-26 14:12:53 UTC 
OK. There are no other packages blocked by the removal. Orphaned.
Comment 10 Denis Fateyev 2019-09-16 16:07:12 UTC 
Whether we need to close this ticket? Because the topic is now cleared (in terms of making the package orphan)
Comment 11 Lumír Balhar 2019-09-16 16:56:52 UTC 
(In reply to Denis Fateyev from comment #10)
> Whether we need to close this ticket? Because the topic is now cleared (in
> terms of making the package orphan)

Please, keep this ticket open. Somebody might want to take over the package and then he/she should fix this issue. If nobody does that, the package will be retired and then we can close this ticket.
Comment 12 Petr Viktorin 2020-10-02 20:11:16 UTC 
Package was retired.
Note You need to log in before you can comment on or make changes to this bug.