View Single Post
Old 10-25-2013, 07:35 AM   #5
At_Libitum
Addict
At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.At_Libitum ought to be getting tired of karma fortunes by now.
 
Posts: 265
Karma: 724240
Join Date: Aug 2013
Device: KyBook
Quote:
Originally Posted by kovidgoyal View Post
I have no clue on how to get the debugger working. I developed all of calibre without ever using a debugger. python has excellent builtin object introspection capabilities, which means that print() is quite sufficient for debugging.
I can imagine that if you wrote the code you know exactly what to expect and where. I on the other hand am trying to look in from the outside without knowing anything much yet from what's inside and need the benefits of visually stepping through code to see how it got there or to try find out which part of the for me totally unknown src is used when performing an action in the gui.
At_Libitum is offline   Reply With Quote