Re: [Py2exe-users] logfile dialog on windows executables

[Thomas H. <th...@py...>]

"Schollnick, Benjamin" <Ben...@xe...> writes:

>> For windows executables, py2exe assigns an object to 
>> sys.stderr that writes the output into a logfile named 
>> <appname>.exe.log, and registers an atexit handler that 
>> displays this messagebox when there has been any output.  
>> Another object is assigned to sys.stdout that simply ignores 
>> everything that is printed to it.  The code doing this is in 
>> Lib\site-packages\py2exe\boot_common.py.
>> 
>> I've been thinking about this - maybe it would be better to 
>> use the logging module for that.
>
> The logging module is not bad....  It's not documented fantastically...
> Or at least it wasn't when I started the logging wrapper that I wrote...
>  
>> I haven't used the logging module myself before. Any ideas?
>
> The following routine will create a log module object...
>
> You can then use it as such....
[...]
Thanks for the code, but this doesn't answer what I wanted to know.

The question is:  Would it be useful to setup a logger in the py2exe
startup code, delivering uncatched exception messages,
sys.stdout/sys.stderr prints, and warnings from the warnings module
to some predefined logger 'channels', and let the application writer
decide where they go?

I've read the new onlamp.com article on logging, and the logging module
seems to be quite powerful and flexible, although also easy to use.
Especially since you can configure it from outside the application via
logging.config.

http://www.onlamp.com/lpt/a/5914

Thomas