MobileRead Forums - View Single Post - Attn plugin developers: calibre moving to Qt 5

kovidgoyal · 07-08-2014, 10:49 PM

Sorry, I was sleeping for the last few hours.

@jacke_w: The use of SIGNAL was deprecated for PyQt4 as well a long time ago. That's why it was removed in PyQt5. As davidfor discovered you simply need to replace it with a new syntax that works in both Qt 5 and Qt4. For example:

Code:

self.connect(action, SIGNAL("triggered()"), slot)

becomes

self.action.triggered.connect(slot)

I will add this to the porting guide.

I dont have any firm plan for when to release calibre 2.0. My idea is to wait and see how the plugin porting goes. Once ~75% of the plugins are ported I will announce a public beta of 2.0 and then depending on how that goes 2.0 will eventually be released. In the meantime, since development of 1.x and 2.x are happening in paralllel I will keep releasing 1.x.

07-08-2014, 10:49 PM	#26
kovidgoyal creator of calibre Posts: 45,455 Karma: 27757438 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Sorry, I was sleeping for the last few hours. @jacke_w: The use of SIGNAL was deprecated for PyQt4 as well a long time ago. That's why it was removed in PyQt5. As davidfor discovered you simply need to replace it with a new syntax that works in both Qt 5 and Qt4. For example: Code: self.connect(action, SIGNAL("triggered()"), slot) becomes self.action.triggered.connect(slot) I will add this to the porting guide. I dont have any firm plan for when to release calibre 2.0. My idea is to wait and see how the plugin porting goes. Once ~75% of the plugins are ported I will announce a public beta of 2.0 and then depending on how that goes 2.0 will eventually be released. In the meantime, since development of 1.x and 2.x are happening in paralllel I will keep releasing 1.x.