View Single Post
Old 01-22-2011, 05:33 AM   #62
pchrist7
Addict
pchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animals
 
pchrist7's Avatar
 
Posts: 385
Karma: 6514
Join Date: Aug 2010
Location: Denmark
Device: Kindle 3 3G+Wifi, Oasis
Quote:
Originally Posted by chaley View Post
Primitively.

I use print statements. Sometimes I toss in stack tracebacks to see how I got to a particular place, but that isn't useful for template functions. Printing does work fine in template functions.

Just in case you don't know: if you open a command box (I think you are running windows?), and run calibre-debug -g, then the debug output (print statements and the like) will show up there. For me, this is more convenient (much faster) than restarting calibre in debug mode and waiting to see the box of output that shows up when you close calibre.
Ahh - never thought of that.
Will try this.
Any way to "set -x" like in most unix shells ?
pchrist7 is offline   Reply With Quote