Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #19344
| From | Rob Richardson <RDRichardson@rad-con.com> |
|---|---|
| Subject | PythonWin debugger holds onto global logging objects too long |
| Date | 2012-01-24 14:52 +0000 |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.5026.1327416731.27778.python-list@python.org> (permalink) |
I use PythonWin to debug the Python scripts we write. Our scripts often use the log2py logging package. When running the scripts inside the debugger, we seem to get one logging object for every time we run the script. The result is that after running the script five times, the log file contains five copies of every message. The only way I know to clean this up and get only a single copy of each message is to close PythonWin and restart it. What do I have to do in my scripts to clean up the logging objects so that I never get more than one copy of each message in my log files? Thank you very much! Rob Richardson
Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread
PythonWin debugger holds onto global logging objects too long Rob Richardson <RDRichardson@rad-con.com> - 2012-01-24 14:52 +0000
Re: PythonWin debugger holds onto global logging objects too long Vinay Sajip <vinay_sajip@yahoo.co.uk> - 2012-02-04 09:09 -0800
Re: PythonWin debugger holds onto global logging objects too long Jean-Michel Pichavant <jeanmichel@sequans.com> - 2012-02-07 11:48 +0100
Re: PythonWin debugger holds onto global logging objects too long Mark Hammond <skippy.hammond@gmail.com> - 2012-02-08 10:04 +1100
csiph-web