View Single Post
Old 05-28-2016, 11:57 PM   #86
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Quote:
Originally Posted by PeterT View Post
Just becasue an error message is displayed regarding PyQt4 does NOT mean the plugin is broken. That means the plugin is supporting both old AND new versions of calibre by using a snippet of code that if it can not load QT4, loads QT5.

I remember back at the time of the move to QT5 having a similar discussion with you where you saw no point accommodating those who could not move to calibre 2.x.
@PeterT:

Wrong. It does not support Qt5. I downloaded the plugin to confirm that the error message was a hard import error, not a "try:except" situation.

Code:
import os, time
import cStringIO
from threading import Thread
from Queue import Queue

from PyQt4.Qt import Qt, QMenu, QFileDialog, QIcon, QPixmap

from calibre import sanitize_file_name

DaltonST
DaltonST is offline   Reply With Quote