New version of DRM removal tools ("DeDRM")

[DNSB]

Originally Posted by Uncle Robin

But the Calibre update was all about fixing something that is at the very least about to be "broke", no? Migrating from Python 2 to 3 now seems like a good idea, rather than waiting for the obsolescence to set in.

Considering that development was started on Python 3 in 2006 and in 2008, it was announced that Jan. 01, 2015 was the EOL for Python 2? Due to complaints, that was extended to Jan. 01, 2020. It is now past the sunset date and yes, it's long past time to move on. In April, 2020, Python 2.7.18 was released which bundled the last fixes to 2.7.17 and that was it for any updates. Your nuclear power station is going to explode? Update the software to Python 3 instead of spending time working around the limitations of Python 2.

[binaryhermit]

Corporate IT policies tend to be pants-on-head stupid.


That said, wasn't Kovid at one point planning to single-handedly maintain Python2 himself rather than port to Python3?

EDIT: Citation for my claim here: https://www.mobileread.com/forums/sh...light=maintain

[Uncle Robin]

Originally Posted by DNSB

Considering that development was started on Python 3 in 2006 and in 2008, it was announced that Jan. 01, 2015 was the EOL for Python 2? Due to complaints, that was extended to Jan. 01, 2020. It is now past the sunset date and yes, it's long past time to move on. In April, 2020, Python 2.7.18 was released which bundled the last fixes to 2.7.17 and that was it for any updates. Your nuclear power station is going to explode? Update the software to Python 3 instead of spending time working around the limitations of Python 2.

Exactly. After reading some of the "waaah, no DeDRM" posts I felt poor Mr Goyal was in a "demned if he did, demned if he didn't" fix - howls of complaints NOW from users of broken pluigins, or howls of complaints LATER when 2's EOL caught up with every user.

[kovidgoyal]

Originally Posted by binaryhermit

That said, wasn't Kovid at one point planning to single-handedly maintain Python2 himself rather than port to Python3?

Yup, porting half a million lines of python 2 to python 3 is too much work. Far more effort than maintaining an existing codebase like python 2. I was actually maintaining a python 2 fork built with Visual Studio 2017 on windows for several years already.

Fortunately, other people showed up to help with the porting to python 3, so it became feasible. See the https://calibre-ebook.com/about#contributors for details.

[pdurrant]

Originally Posted by kovidgoyal

Yup, porting half a million lines of python 2 to python 3 is too much work.

Even porting the 22,000+ lines of the DeDRM script seems to be quite a lot of work.

[pwalker8]

As a developer who has had to port code to new versions of a language, let me say that sometime porting can be a major, major effort. The non programmers tend to say "what's the big deal, just recompile it", but depending on the language and the release, it can be a lot of work. And it's all grunt work, which few actually want to do. A lot of stuff breaks.

[pwalker8]

For anyone who is interested -

On my mac, I copied my Calibre 4.23 app to a new name(calibre4-23) in the app folder
. I installed Calibre 5.1. That runs fine. DeDRM does not work. However, I was able to run Calibre 4.23 (I first had to stop Calibre 5.1) and remove the DRM with Calibre 4.23. I think shutdown Calibre 4.23 and restarted Calibre 5.1. The DeDRM'ed book was there, no problem. I was able to convert it to epub and read it, no problem.

I'm not sure how you would do this with windows or linux, but I suspect a similar set up would work.

I had no problem connecting to Calibre 5.1 with the current version of Calibre Companion for iOS and downloading the book, both as a wireless device and content server.

[JSWolf]

Originally Posted by pwalker8

For anyone who is interested -

On my mac, I copied my Calibre 4.23 app to a new name(calibre4-23) in the app folder
. I installed Calibre 5.1. That runs fine. DeDRM does not work. However, I was able to run Calibre 4.23 (I first had to stop Calibre 5.1) and remove the DRM with Calibre 4.23. I think shutdown Calibre 4.23 and restarted Calibre 5.1. The DeDRM'ed book was there, no problem. I was able to convert it to epub and read it, no problem.

I'm not sure how you would do this with windows or linux, but I suspect a similar set up would work.

I had no problem connecting to Calibre 5.1 with the current version of Calibre Companion for iOS and downloading the book, both as a wireless device and content server.

On Windows, install 4.23 portable alongside a 64-bit install of 5.1. Then you can copy your setting to the portable settings That's what I did except I have 5.1 as portable.

[Lynx-lynx]

A query, if I uninstall Caibre 5.1 and then install calibre 4.23.0, will I lose all my ebooks and their respective attributes? (2,145 ebooks)

[JSWolf]

Originally Posted by Lynx-lynx

A query, if I uninstall Caibre 5.1 and then install calibre 4.23.0, will I lose all my ebooks and their respective attributes? (2,145 ebooks)

You will not lose your settings (including the plugins) and you will not lose your library.

[Lynx-lynx]

Yes that worked thank you

[ZodWallop]

Originally Posted by JSWolf

On Windows, install 4.23 portable alongside a 64-bit install of 5.1. Then you can copy your setting to the portable settings That's what I did except I have 5.1 as portable.

I don't understand the point of installing two versions of Calibre. What are the benefits of running two versions? What killer new feature does Calibre 5 bring that makes it necessary to run alongside 4.23?

I installed 5, but once I saw de-DRM doesn't work I rolled back to 4.23 and will wait for everything to sort itself out.

[JSWolf]

Originally Posted by ZodWallop

I don't understand the point of installing two versions of Calibre. What are the benefits of running two versions? What killer new feature does Calibre 5 bring that makes it necessary to run alongside 4.23?

I installed 5, but once I saw de-DRM doesn't work I rolled back to 4.23 and will wait for everything to sort itself out.

I have the portable version of Calibre 5.x installed for testing plugins including the DeDRM plugin when it's actually ready to test.

[ratinox]

Can I reiterate the request to keep this to announcements of new versions of the tools? This is not the place for discussion.
Thank you.

[pwalker8]

Originally Posted by ZodWallop

I don't understand the point of installing two versions of Calibre. What are the benefits of running two versions? What killer new feature does Calibre 5 bring that makes it necessary to run alongside 4.23?

I installed 5, but once I saw de-DRM doesn't work I rolled back to 4.23 and will wait for everything to sort itself out.

It really comes down to if you believe in keeping your software up to date or not. I just find that I runs into less issues keeping my software up to date.