View Single Post
Old 10-25-2013, 12:26 PM   #7
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
Again, I know about traceback, I know about pdb, have tried both, neither of them gives me what I need. Plus that with inserting print at every possible location is a hit or miss if you don't know the code

You may not need a debugger, but those basic means do not provide me the information to understand what and why. I need to be able to step-thru for that.

Anyone else here using Aptana/Eclipse on Windows and is able to step through their plugin code?

My current setup is Aptana with PyDev, code analysis/undefined filled in as advised, Qt is installed, Python2.7 is installed, Calibre src pulled from git in a new Aptana project, everything up to here works. I can browse the code just fine without Aptana complaining about missing references, but I could do that already with grep and pspad

According to info found here I need to add

import pydevd
pydevd.settrace()

in my code, so did that but then Calibre just bombs the moment I start it.

So I cannot even get it to go through calibre's python src, let alone my plugin attempt.

Last edited by At_Libitum; 10-25-2013 at 12:29 PM.
At_Libitum is offline   Reply With Quote