View Single Post
Old 12-18-2019, 12:36 PM   #36
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 kovidgoyal View Post
I dont see how calibre 4.99 will fail at startup regardless of what UI plugins do, unless those UI plugins mess with sys.path, or other global interpreter state, which is the case with all versions of calibre.

See your answer to this post:https://www.mobileread.com/forums/sh...82&postcount=9



which you provided here: https://www.mobileread.com/forums/showpost.php?p=3929798&postcount=15


Quote:
@DaltonST: Likely one of those plugins is causing the issue them, run calibre as

calibre --ignore-plugins
You were correct. calibre --ignore-plugins allowed 4.99 to start up. Otherwise, back to my original post at https://www.mobileread.com/forums/sh...82&postcount=9


Remember that virtually ALL plugins will fail in 4.99 unless they are ported to Python 3 first. Users will have no idea why Calibre silently dies on them. Hence, user mass confusion.



DaltonST

Last edited by DaltonST; 12-18-2019 at 12:45 PM.
DaltonST is offline   Reply With Quote