View Single Post
Old 07-05-2012, 02:23 PM   #44
kiwidude
Calibre Plugins Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,733
Karma: 2197770
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
Sure you "could" - but it means yet another way of doing things that won't work when suddenly your test code needs a library or function that is in calibre. Which happens *alot* for me at least. So rather than have to deal with two different ways of doing things just because a line or two of your test code has changed I gave Agama the simplest answer which has worked for me.

I just keep a command line window open to run calibre-debug -e with (a simple up-arrow enter to re-run things), and edit the test file within Eclipse along with the plugin code. You still get all the code analysis checking of the IDE, but can run *any* code be it 100% python only or a mixture using the same approach.
kiwidude is offline   Reply With Quote