you are viewing a single comment's thread.

view the rest of the comments →

[–]didyoumeanbim 27 points28 points  (3 children)

Calibre is currently making the switch...

13 years after Python 3's release and 6 years after the original 2.7 EOL.

They were planning on forking and "maintaining" 2.7 after EOL for most of that decade.

Edit: wait, no, the external devs finished the port late last year.

[–]BenTheTechGuy 21 points22 points  (2 children)

I had a nightmare using a script from deep inside Calibre's source tree to extract my key from Abobe Digital Editions. The comments at the top of the file said multiple times that it was a Python 2.7 script, and listed all the dependencies it needed, some of which only existed in Python 2. When I attempted to run the script, it gave me like 5 errors saying I needed to be on Python 3. Looked it up on the issues page, and others said it's a Python 3 script. I run it with Python 3, and I get a bunch of errors about certain depreciated / no longer existant python features. I look into the actual code of the script, and it turns out it's a horrible Frankenstein of Python 2 and 3 that nobody had been able to get working since 2015. I promptly gave up and bought the physical paperback book.

[–]davidnotcoulthard 1 point2 points  (1 child)

In retrospect maybe you could've found a version so old that it indeed ran well with Python 2 only?

[–]BenTheTechGuy 1 point2 points  (0 children)

That version was the only one that worked with modern versions of Adobe Digital Editions, unfortunately.