John Gordon wrote:
If I didn't do all that in a class, where would I do it?
I find the configureLoggers method of ZConfig most convenient for this:
http://pypi.python.org/pypi/ZConfig
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://
Vinay Sajip wrote:
I'm not sure why you need all the code you've posted. The logging
package allows you to add tracebacks to your logs by using the
exception() method, which logs an ERROR with a traceback and is
specifically intended for use from within exception handlers.
You can also use the
On Sep 28, 9:38 pm, John Gordon wrote:
>
> If I didn't do all that in a class, where would I do it?
>
You could, for example, use the basicConfig() function to do it all
for you.
import logging
logging.basicConfig(filename='/path/to/my/log',level=logging.DEBUG)
logging.debug('This message shoul
l, avoid adding handlers more than once - which you are
>> almost guaranteed to not avoid if you do this kind of processing in a
>> constructor. If you write your applications without using the
>> exceptionLogger class (not really needed, since logging exceptions
>> with tracebacks
do this kind of processing in a
> constructor. If you write your applications without using the
> exceptionLogger class (not really needed, since logging exceptions
> with tracebacks is part and parcel of the logging package's
> functionality since its introduction with Python 2.3),
ng the
exceptionLogger class (not really needed, since logging exceptions
with tracebacks is part and parcel of the logging package's
functionality since its introduction with Python 2.3), what
functionality do you lose?
Regards,
Vinay Sajip
--
http://mail.python.org/mailman/listinfo/python-list
I wrote some code to handle and log exceptions in my application.
It works well, but it produces double output for each exception.
How can I fix this?
Here's the pared-down code:
- main.py
import exceptionLogger
import doStuff
exlog = exceptionLogger.exceptionLogger()
stuff = doStuff.doStuf
On May 7, 1:19 pm, Pierre GM wrote:
> On May 7, 5:32 am, Lie Ryan wrote:
>
>
>
> > Pierre GM wrote:
> > > All,
> > > I need to log messages to both the console and a given file. I use the
> > > following code (on Python 2.5)
>
> > import logging
> > #
> > logging.basicConfig(level=
>
>
> > > So far so good, but I'd like to record (possibly unhandled) exceptions
> > > in the logfile.
> > > * Do I need to explicitly trap every single exception ?
> > > * In that case, won't I get 2 log messages on the console (as
> > > illustrated in the code below:
>
Check out sys.excepthook,
On May 7, 5:32 am, Lie Ryan wrote:
> Pierre GM wrote:
> > All,
> > I need to log messages to both the console and a given file. I use the
> > following code (on Python 2.5)
>
> import logging
> #
> logging.basicConfig(level=logging.DEBUG,)
> logfile = logging.FileHandler('log.l
Pierre GM wrote:
All,
I need to log messages to both the console and a given file. I use the
following code (on Python 2.5)
import logging
#
logging.basicConfig(level=logging.DEBUG,)
logfile = logging.FileHandler('log.log')
logfile.setLevel(level=logging.INFO)
logging.getLogger('').addHandler(l
In message <597627b8-
d30b-4b74-9202-9cd46fb1d...@s28g2000vbp.googlegroups.com>, Pierre GM wrote:
> ... I'd like to record (possibly unhandled) exceptions in the logfile.
python myscript.py 2>error.log
--
http://mail.python.org/mailman/listinfo/python-list
All,
I need to log messages to both the console and a given file. I use the
following code (on Python 2.5)
>>> import logging
>>> #
>>> logging.basicConfig(level=logging.DEBUG,)
>>> logfile = logging.FileHandler('log.log')
>>> logfile.setLevel(level=logging.INFO)
>>> logging.getLogger('').addHandl
On Aug 27, 10:30 am, Rob Wolfe <[EMAIL PROTECTED]> wrote:
> Vinay Sajip napisa³(a):
>
>
>
> > On Aug 26, 10:36 am, Alexandru Mosoi <[EMAIL PROTECTED]> wrote:
> > > why doesn'tloggingthrow any exception when it should? how do I
> > > configureloggingto throw exceptions?
>
> > > >>> try:
>
> > > ...
Vinay Sajip napisał(a):
> On Aug 26, 10:36 am, Alexandru Mosoi <[EMAIL PROTECTED]> wrote:
> > why doesn'tloggingthrow any exception when it should? how do I
> > configureloggingto throw exceptions?
> >
> > >>> try:
> >
> > ... logging.fatal('asdf %d', '123')
> > ... except:
> > ... print 'thi
On Aug 26, 10:36 am, Alexandru Mosoi <[EMAIL PROTECTED]> wrote:
> why doesn'tloggingthrow any exception when it should? how do I
> configureloggingto throw exceptions?
>
> >>> try:
>
> ... logging.fatal('asdf %d', '123')
> ... except:
> ... print 'this line is never printed'
> ...
> Traceback (
Alexandru Mosoi napisał(a):
> why doesn't logging throw any exception when it should? how do I
> configure logging to throw exceptions?
>
> >>> try:
> ... logging.fatal('asdf %d', '123')
> ... except:
> ... print 'this line is never printed'
> ...
[...]
You need to subclass your handler and
why doesn't logging throw any exception when it should? how do I
configure logging to throw exceptions?
>>> try:
... logging.fatal('asdf %d', '123')
... except:
... print 'this line is never printed'
...
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/2
On Jan 14, 5:46 pm, Karsten Hilbert <[EMAIL PROTECTED]> wrote:
> Dear all,
>
> I have a problem withloggingan exception.
>
> environment:
>
> Python 2.4, Debian testing
>
> ${LANGUAGE} not set
> ${LC_ALL} not set
> ${LC_CTYPE} not set
> ${LANG}=de_DE.UTF-8
>
Dear all,
I have a problem with logging an exception.
environment:
Python 2.4, Debian testing
${LANGUAGE} not set
${LC_ALL} not set
${LC_CTYPE} not set
${LANG}=de_DE.UTF-8
activating user-default locale with returns: [de_DE.UTF-8]
local
20 matches
Mail list logo
