New version of DRM removal tools ("DeDRM")

[pdurrant]

When you update, the old preferences should carry over.

[JSWolf]

Originally Posted by Sirtel

You can use the old plugin. I have not updated my tools for years, because there's been no need. They work fine. Update when you run into problems.

That's what I do. I have an oldish version of the DeDRM plugin. But it works so I've seen no reason to update. I'm running 6.3.3.

[JSWolf]

Originally Posted by curtw

I recently bought a nook GlowLight Plus, and do had to upgrade Calibre to a version that "knows" this device. My existing tools plug-in (version 6.0.7) still works fine, but if I try to reconfigure it, I get an error, "AttributeError: 'module' object has no attribute 'ConfigWidget'"

Should I just leave it alone, and continue to use my old plug-in? If I update to the latest, will I have to re-enter all of the appropriate keys?

Given that the version you are using no longer allows configuration, I would update to the current version. All your existing data carries over.

[hollowpoint]

I had occasion to install the latest DeDRM, add my PW4 serial, and liberate a few new books. Worked perfectly!

Thanks again to those who contribute to the project.

[jsessions]

No longer works with Calibre now that Calibre has updated to v5.0 & Python 3. I've kept a copy of Calibre Portable 4.23 for when/if plugin is needed. Hopefully DeDRM will be updated in due course.

[ApK]

Thanks for the warning, I'll stay on calibre 4 for now.

[alansplace]

Originally Posted by jsessions

No longer works with Calibre now that Calibre has updated to v5.0 & Python 3. I've kept a copy of Calibre Portable 4.23 for when/if plugin is needed. Hopefully DeDRM will be updated in due course.

Originally Posted by ApK

Thanks for the warning, I'll stay on calibre 4 for now.

I'll be sticking with 4.23 too, I was lucky to have read your post before I ran Calibre this morning and was offered the upgrade to 5.01!!

[pwalker8]

Is there some reason you can't simply re-install the older version?

[DiapDealer]

Not to give people a hard time or anything, but this has been a major topic of concern in the calibre forums since the beta of calibre 5 was announced. Plugin devs have had since about February to get their plugins ready to work with this new release. This plugin is not the only one that won't work with the new calibre.

The fact is that this--and other plugins--were going to stop working with calibre 5 should really only be news to people who never visit the calibre forums.

[ApK]

Originally Posted by DiapDealer

The fact is that this--and other plugins--were going to stop working with calibre 5 should really only be news to people who never visit the calibre forums.

I would bet that is a lot of people.
I'm a calibre user, not a calibre hobbyiest, and thanks to the fact that calibre has generally worked without the need for support since I first got it working with the plugin, i almost never visit the forums.

[jhowell]

It is unfortunate that Apprentice Harper appears to no longer have any time to devote to this project. Perhaps a new "Apprentice" will step up and take over from Harper as Harper once did from Alf.

[John F]

Originally Posted by ApK

I would bet that is a lot of people.
I'm a calibre user, not a calibre hobbyiest, and thanks to the fact that calibre has generally worked without the need for support since I first got it working with the plugin, i almost never visit the forums.

+1

I'm still on Calibre 3.34.

[DNSB]

Originally Posted by pwalker8

Is there some reason you can't simply re-install the older version?

The old version is Python 2 compatible. Calibre 5.0.1 requires Python 3 compatibility. There is a Python 3 branch of the DeDRM 6.6.3 code however it has issues (run the make_release.py file and the resultant .zip will not install due to errors in _init_.py).

[jhowell]

Originally Posted by pwalker8

Is there some reason you can't simply re-install the older version?

Originally Posted by DNSB

The old version is Python 2 compatible. Calibre 5.0.1 requires Python 3 compatibility....

Perhaps pwalker8 meant to re-install the old version of calibre. That will work to restore DeDRM, but beware!

Once you open a library in Calibre 5 it changes it in a way that is potentially incompatible with calibre versions prior to 4.23. So if you revert do not use an older version of calibre than that one.

From "Backwards incompatibilities" in New in calibre 5.0:

Because of the support for library wide annotations, the database format was slightly changed. While calibre 4.23 is able to open and operate with calibre 5 databases, older versions of calibre may have trouble.

[cromag]

Originally Posted by DiapDealer

Not to give people a hard time or anything, but this has been a major topic of concern in the calibre forums since the beta of calibre 5 was announced. Plugin devs have had since about February to get their plugins ready to work with this new release. This plugin is not the only one that won't work with the new calibre.

The fact is that this--and other plugins--were going to stop working with calibre 5 should really only be news to people who never visit the calibre forums.

Well, I wouldn't say I never go there, but I only go there when I have a problem -- which isn't very often.

Thanks for the heads up!