Bug 1738083

Summary:	macromilter depends on Python 2
Product:	[Fedora] Fedora	Reporter:	Lumír Balhar <lbalhar>
Component:	macromilter	Assignee:	Robert Scheck <redhat-bugzilla>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	mhroncok, pviktori, redhat-bugzilla
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-11-16 11:55:27 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, 1739524, 1770609, 1770610

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

Thank you.

Comment 1 Ben Cotton 2019-08-13 16:49:05 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:08:24 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 Robert Scheck 2019-08-14 09:46:20 UTC

Thank you for filing this report. I'm already aware about this issue and thus already talked to upstream some months ago. As of writing, the software is written in Python 2 due to Python3-PyMilter being Python2-only for a very long time (compared to other Python modules). Upstream will work on Python 3 support, however, this is likely to be addressed late, thus closed to the Python 2.7 EOL date.

Comment 4 Lumír Balhar 2019-08-21 13:31:57 UTC

Thank you for the info.

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 Petr Viktorin (pviktori) 2019-09-30 12:01:21 UTC

Let us know if/when you have better information on Python 3 support -- specifically, if it can be done by mid-November or not.


Below is a list of macromilter's dependencies that need Python 2.
If you're planning to keep macromilter in Fedora after mid-November, please get in touch with the packagers. Some already have bugs like this one, where we ask for the plans regarding Python 2.
A FESCo exception for macromilter would need to include all these dependencies (unless you can reduce some).

- python2-configparser
  - python2-backports (https://bugzilla.redhat.com/show_bug.cgi?id=1739541 -- to be removed when its dependents are gone)
  - python2-setuptools (https://bugzilla.redhat.com/show_bug.cgi?id=1747850 -- please co-maintain it if you need it)
- python2-oletools (yours)
  - python2-pyparsing
  - python2-colorclass
  - python2-easygui
  - python2-olefile (yours)
  - python2-prettytable
- python2-pymilter
  - python2-pydns (https://bugzilla.redhat.com/show_bug.cgi?id=1739524)
- python27

Comment 6 Petr Viktorin (pviktori) 2019-11-01 13:37:35 UTC

Is this on track for mid-November, or does it need an exception?

Comment 7 Miro Hrončok 2019-11-10 12:54:58 UTC

See also bz1770551.

Comment 8 Robert Scheck 2019-11-10 13:37:39 UTC

It seems like upstream won't be able to deliver in-time and given bug #1770551 I guess it's easier to orphan on rawhide only and do a new package review later?

Comment 9 Miro Hrončok 2019-11-10 15:16:16 UTC

IMHO retiring this o rawhide and resurrecting it after it is ready is the best thing to do here. We are glad to help with the review then.

Comment 10 Robert Scheck 2019-11-16 11:55:27 UTC

macromilter-3.7.0-0.2.20191111git2761838.fc32 uses Python 3 now (thanks Michal!), even upstream might have still work left.