Bug 1737817

Summary:	mailnag depends on Python 2
Product:	[Fedora] Fedora	Reporter:	Lumír Balhar <lbalhar>
Component:	mailnag	Assignee:	Thorsten Leemhuis <fedora>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	fedora
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-10-31 07:01:44 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 09:32:30 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 mailnag'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?) [remove if clear]

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

Thank you.

Comment 1 Ben Cotton 2019-08-13 17:54:36 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 2 Lumír Balhar 2019-08-14 09:07: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, please let us know.

Comment 3 Thorsten Leemhuis 2019-08-14 12:05:50 UTC

Sorry for the delay, here we go:

(In reply to Lumír Balhar from comment #0)
>
> - What is the reason for the Python2 dependency? 

Software is not ported to Python3 yet

> - What are the upstream/community plans/timelines regarding Python 3?

No timeline, just a early version of a python3 port for now (and not progress recently afaics)
https://github.com/pulb/mailnag/issues/121

> - 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?)

Afaics: Help upstream.

Comment 4 Lumír Balhar 2019-08-15 06:37:37 UTC

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, and nothing in Fedora uses it, you can retire it or just remove the Python 2 part from it (subpackage, module, bindings, etc.).

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 5 Thorsten Leemhuis 2019-10-30 19:30:51 UTC

(In reply to Thorsten Leemhuis from comment #3)
> > - What are the upstream/community plans/timelines regarding Python 3?
> No timeline, just a early version of a python3 port for now 

Good news, there is WIP now that is in a testable state now, hence after taking to the upstream maintainer I pushed the python3 port to rawhide (https://bodhi.fedoraproject.org/updates/FEDORA-2019-8d94aacb1d). What else do I have to do to make sure mailnag is not getting removed mid November? And can we close this bug or is it needed for additional tracking?

Comment 6 Lumír Balhar 2019-10-31 07:01:44 UTC

I can confirm that the latest build does not depend on Python 2 anymore. Good job!

Nothing more is needed here. Just make sure to track the development and keep rawhide updated.