Python 2 is retiring

Bug #1714107 reported by Darwin Wu on 2017-08-30
This bug affects 5 people
Affects Status Importance Assigned to Milestone

Bug Description

Python 2 is retiring in thirty months. Calibre needs to convert to Python 3.

No, it doesn't. I am perfectly capable of maintaining python 2 myself.
Far less work than migrating the entire calibre codebase.

 status wontfix

Changed in calibre:
status: New → Won't Fix
Sean (sean.brady) wrote :


I sincerely hope this is a joke.

Andrew Rabert (nvllsvm) wrote :

I strongly urge you to reconsider this. Unless others begin contributing to your fork of Python 2.7, you're probably going to miss a number of future security issues, make building and deployment more complex, and break compatibility with the Python packages Calibre depends upon.

I've started working on getting Calibre running under both Python 2 and 3. Are you open to patches provided they do not negatively impact anything?

Kovid has stated numerous times that any patches which work towards
python3 compatibility without hurting python2 functionality or
performance would be happily accepted. Oddly enough, no one has ever
taken him up on that, though a number of people have insisted it is
*very important* that he himself do that work.

See e.g. bug 1456642 or bug 1756458

No, past offers to donate the computing power to run the 2to3 tool for
low-quality, non-polyglot, python3-only results don't count as valid

Eli Schwartz (eschwartz) wrote :

Also note that there is sure to be at least one of several different
organizations who will be more than happy to maintain Python 2 forks,
for example Red Hat and other distros whose commercial extended support
will continue to provide python2.

Hellmark (spamtrap-hellmark) wrote :

Eli, problem is, most of those commercial distros aren't really used on the desktop. Asking people to use RHEL isn't really feasible. Plus you'll have distros like Debian that don't accept bundled applications.

Eli Schwartz (eschwartz) wrote :

I have no clue what you're talking about. Why would Red Hat as an upstream source for python2 be any more objectionable than the Python Software Foundation?

You know, that Red Hat are the upstream developers for lots of software available on a wide variety of Linux distributions?

Anyway, this is quite beside the point. See and followup Pull Requests, where someone has graciously put in a fair amount of effort towards supporting python3. You can now use python3 to try building calibre after exporting the environment variable "CALIBRE_PY3_PORT" to check out the progress -- so far, basic 2to3 tidying up has been done, and the compiled extensions should compile without errors on python3 -- anything more complex than that will need more work, but that's at least enough to play around with it and see what major fixes are needed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers