(In reply to Lumír Balhar from comment #0)
> To help planning, we'd like to know the plans for exaile'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?) 

Exaile is written in Python 2 and has 2 optional dependencies available only in python 2 (python-CDDB, to be replaced by a different library soon; python2-spydaap which is not even packaged for Fedora).

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

There is no timeline, only a vague plan. See https://github.com/exaile/exaile/issues/246
 
> - 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?)

If you want to contribute, please see https://github.com/exaile/exaile/issues/246

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

(In reply to Ben Cotton from comment #2)
> This bug appears to have been reported against 'rawhide' during the Fedora
> 31 development cycle.
> Changing version to '31'.

Moved to back to rawhide as this won't be addressed in f31 release cycle.

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

If upstream doesn't port to python3 in time for that I will have to retire it.

This is now broken on Rawhide:

DEBUG util.py:596:  2019-11-27 07:49:56,797: Problem: conflicting requests
DEBUG util.py:596:  2019-11-27 07:49:56,798: - nothing provides python2-gstreamer1 >= 1.4 needed by exaile-4.0.0-3.fc31.noarch.
DEBUG util.py:596:  2019-11-27 07:49:56,798: 

it is breaking the MATE live image build.

https://github.com/exaile/exaile/issues/608 seems to be discussed upstream as the 'last' Python 2-only dependency. There is a PR open but not merged that has not been touched since August: https://github.com/exaile/exaile/pull/652

Since it looks like this isn't moving very fast upstream, I think we should drop Exaile from the MATE image to make it build again. Not sure what should replace it. CCing raveit65 (MATE spin maintainer) for that.

This also affects the Cinnamon live image, so CCing Dan. Dan, fedora-cinnamon-common.ks includes exaile and that means Cinnamon image builds fail in current Rawhide because of this bug, it probably needs replacing.

*** This bug has been marked as a duplicate of bug 1777624 ***

Is there any chance to get it back if upstream manages to get it ported to python3? If yes, when would be the deadline?

Yes, if we get it Python 3 based, we can get it back.

Withing 8 weeks of retirement, we can get i back without a Fedora review. But we can get it back with a review any time. I'll gladly do the review, juts ping me when ready.


If we want to have it back withing Fedora 32 release, the deadline is Final Freeze: 2020-04-07

https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html

Just to note that I have taken over maintenance for Exaile and I'm currently in the process of bringing it back to the current release branches.