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 1738082 - mailman depends on Python 2
Summary: mailman depends on Python 2
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mailman
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
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-06 12:51 UTC by Lumír Balhar
Modified: 2021-05-11 11:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-11 11:06:46 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Lumír Balhar 2019-08-06 12:51:20 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 mailman'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 mailman.
If you need anything from us, or something is unclear, please mention it here.

Thank you.
Comment 1 Pavel Zhukov 2019-08-07 08:44:09 UTC 
(In reply to Lumír Balhar from comment #0)
> 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 mailman'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?) 
Mailman 2 is Python 2  only application. It supposed to be compatible with python 2.4 even.
> 
> - What are the upstream/community plans/timelines regarding Python 3?
Mailman 2 will not be ported to Py3 by upstream as it in maintenance mode.  
I'm working on porting.
> 
> - 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?)
> 
The main problem is mess with bytes/strings during the porting. Besides of that python-email module is not perfect.
> 
> This bug is filed semi-automatically, and might not have all the context
> specific to mailman.
> If you need anything from us, or something is unclear, please mention it
> here.
> 
> Thank you.
Thank you for reporting this bug one week before devel freeze...
Comment 2 Petr Viktorin 2019-08-07 16:10:28 UTC 
> Thank you for reporting this bug one week before devel freeze...

Python 2 will be retired in Fedora 32. The upcoming devel freeze is for f31.
Comment 3 Ben Cotton 2019-08-13 16:59:45 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.
Comment 4 Ben Cotton 2019-08-13 17:34:22 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.
Comment 5 Lumír Balhar 2019-08-15 07:12:08 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 6 Miro Hrončok 2019-11-28 01:17:58 UTC 

*** This bug has been marked as a duplicate of bug 1777634 ***
Comment 7 Miro Hrončok 2021-01-06 16:02:26 UTC 
> Mailman 2 will not be ported to Py3 by upstream as it in maintenance mode.  
> I'm working on porting.

Has there been any update wrt the porting work?
Comment 8 Miro Hrončok 2021-03-17 00:31:41 UTC 
Has there been any update wrt the porting work?
Comment 9 Fedora Admin user for bugzilla script actions 2021-04-02 00:47:51 UTC 
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Comment 10 Miro Hrončok 2021-05-11 11:06:46 UTC 
Automation has figured out the package is retired in rawhide.

If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement
Note You need to log in before you can comment on or make changes to this bug.