Christoph Haas wrote:
> Thanks. That works great. I was looking for a way to close the log file
> using logging.basicConfig but it appears that it's too much magic.
> logging.getLogger() isn't really much more work but gives better
> control.
You may also need to close the handler - removeHandler
On Wed, Jun 14, 2006 at 12:29:22PM +0530, Amit Khemka wrote:
> On 6/13/06, Christoph Haas <[EMAIL PROTECTED]> wrote:
> >I have an application that is running in an endless loop processing an
> >incoming queue. Every run is supposed to write a log file about the run
> >and then close it again. While
On 6/13/06, Christoph Haas <[EMAIL PROTECTED]> wrote:
> Evening,
>
> I have an application that is running in an endless loop processing an
> incoming queue. Every run is supposed to write a log file about the run
> and then close it again. While the 'logging' module is generally working
> well (ev
Evening,
I have an application that is running in an endless loop processing an
incoming queue. Every run is supposed to write a log file about the run
and then close it again. While the 'logging' module is generally working
well (even though the documentation makes me miss some proper examples
ho
