Re: Logging insights for Gump3 please

2005-04-26 Thread Leo Simons
On 26-04-2005 02:10, Adam R. B. Jack [EMAIL PROTECTED] wrote: Change config.py; configure the logging package by hand (I think that's called basicConfig()) instead of using a config file, and make it output everything to the screen. We can fix it later, and there's no test to look for the

Re: Logging insights for Gump3 please

2005-04-26 Thread Adam R. B. Jack
OTOH, debug statements have also worked reasonably for ages. Simplest thing, simplest thing ;) Yup, I'm there for now, however I was thinking about communication between two separate developers of plugins, perhaps the latter not being able to hack debug statements into the former. Still, right

Re: Logging insights for Gump3 please

2005-04-25 Thread Leo Simons
On 25-04-2005 00:24, Adam R. B. Jack [EMAIL PROTECTED] wrote: I'm still finding it hard to make progress, 'cos I can't see log output. This (captured below) is all I see, and either there is a problem with logging on (Cygwin) or the Mutliplexer isn't dispatching, or something. Do we need to

Re: Logging insights for Gump3 please

2005-04-25 Thread Adam R. B. Jack
Change config.py; configure the logging package by hand (I think that's called basicConfig()) instead of using a config file, and make it output everything to the screen. We can fix it later, and there's no test to look for the existence of log files so you're not breaking anything ;) Ok,

Re: Logging insights for Gump3 please

2005-04-24 Thread Adam R. B. Jack
I'm still finding it hard to make progress, 'cos I can't see log output. This (captured below) is all I see, and either there is a problem with logging on (Cygwin) or the Mutliplexer isn't dispatching, or something. Do we need to ask for non-buffered log files, or do some flushing prior to exit,

Logging insights for Gump3 please

2005-04-19 Thread Adam Jack
I learn a program's behaviour from watching it's logs. I want to see the Gump3 logs, but am getting a headache trying to figure out how: 1) Why is there a long pause before logs start spewing when one does --debug? Is some file buffered? How can I get spew as you go behaviour so I can 'watch' it?

Re: Logging insights for Gump3 please

2005-04-19 Thread Adam R. B. Jack
I dunno. Could be. Could you be a little more specific about what you're seeing and when what pauses? On every 'run' invocation the 'gump' shell scripts removes *.pyc then recompiles and re-imports, that's part of the delay. It seems like the program runs, and only once done I see output.