Bug 1731396 - calibre depends on Python 2 and cannot be installed
Summary: calibre depends on Python 2 and cannot be installed
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: calibre
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1667497
Blocks: F31FailsToInstall PY2FTBI F31_PY2REMOVAL
TreeView+ depends on / blocked
 
Reported: 2019-07-19 10:24 UTC by Lumír Balhar
Modified: 2019-08-20 11:31 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-20 11:31:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lumír Balhar 2019-07-19 10:24:01 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 calibre's future. Specifically:

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

Thank you.

Comment 1 Zbigniew Jędrzejewski-Szmek 2019-07-19 12:19:37 UTC
We're working on it.

Comment 2 Miro Hrončok 2019-07-22 16:01:08 UTC
Also note: nothing provides python2-apsw needed by calibre-3.36.0-7.fc31.x86_64

Comment 3 Kevin Fenzi 2019-07-22 16:26:05 UTC
Right, this is not built for rawhide due to that...

Comment 4 Miro Hrončok 2019-07-31 10:41:51 UTC
Will calibre need an exception for Fedora 32, or the plan is to get it switched before that? Do you have an idea about timeframe here?

Thanks.

Comment 5 Miro Hrončok 2019-08-05 15:31:24 UTC
$ mock -r fedora-rawhide-x86_64 init
$ mock -r fedora-rawhide-x86_64 install calibre
Problem: conflicting requests
 - nothing provides python2-apsw needed by calibre-3.36.0-7.fc31.x86_64

Comment 6 Ben Cotton 2019-08-13 16:50:41 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 7 Ben Cotton 2019-08-13 18:32:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 8 Lumír Balhar 2019-08-14 07:52:59 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 9 Kevin Fenzi 2019-08-14 22:35:04 UTC
Yes, we need to get https://bugzilla.redhat.com/show_bug.cgi?id=1719008 reviewed, then we can move to python3 calibre. 

See discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1667497

I'll try and review that soon if no one else can, but might be not until the weekend.

Comment 10 Zbigniew Jędrzejewski-Szmek 2019-08-20 11:31:41 UTC
Built in rawhide and F31.
calibre should now run under python3.


Note You need to log in before you can comment on or make changes to this bug.