View Single Post
Old 12-18-2019, 12:31 PM   #33
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
Kovid,

Given that Calibre 4.99 will silently fail at startup with no indication as to the cause if a UI plugin that is not compatible with Python 3 is initialized, and given that many users have many plugins, IMHO it might be prudent to add a new attribute to InterfaceActionBase that defaults to False and means that the respective UI plugin is "safe" to use with Python 3 Calibre only when the plugin returns True for that new attribute. This should help to avoid needless user mass confusion and panic in the future.


DaltonST

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