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? 2) Why do some things (like "DEBUG - Outputting all log data (a lot)...") come out to the console, but not the rest of the logging information? [I see that rather than fork another process for the "pygump engine run" we import and run it. I assume that and SVN run (updating the pygump/.../*.py file) ought not be imported at that point, but I feel like I'm seeing what feels like a log 'bleed' that suggests otherwise.] 3) I'd like to understand logging in parts ... (1) gump (2) main (3) pygump. I suspect that there is a redirect in (1) that I'd like to change to a 'tee', but can't find it. [BTW: I once tried using Python to test if stdout was to a console, or not, but I never seemed to get correct behaviour (on Windows, at least).] BTW: I tried writing a pretty print plug-in, but I believe that is what logreporter is meant to do. unfortunately, for me, the promised "lots of data" fails to appear. Any clues why? regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
