On Dec 1, 2011, at 12:32 PM, Tom Sheffler wrote:
> 1) we use multiple logfiles. one for *all* messages, and another for
> *special* messages. It would be nice if the concept of multiple logfiles and
> the routing of messages to files was part of the system.
You could implement this by having
On 11/30/2011 5:20 AM, exar...@twistedmatrix.com wrote:
> On 29 Nov, 06:44 pm, ddwigg...@advpubtech.com wrote:
>> Looking at the source of log.py, I'm at a bit of a loss to reconcile
>> these two forces. Certainly, the two log observers implemented there
>> use textFromEventDict, but one could cr
I am happy with the information I get out of the logging system and the
formatting of errors and tracebacks. We've recently come across two things
that could be handled nicer however.
1) we use multiple logfiles. one for *all* messages, and another for
*special* messages. It would be nice if th
On Nov 30, 2011, at 9:57 PM, Tim Allen wrote:
> On Wed, Nov 30, 2011 at 01:04:27PM -, exar...@twistedmatrix.com wrote:
>> On 04:07 am, screwt...@froup.com wrote:
>>> If the standard Twisted logging functions automatically constructed
>>> LogMessage instances from dict instances, it should be
On Wed, Nov 30, 2011 at 01:04:27PM -, exar...@twistedmatrix.com wrote:
> On 04:07 am, screwt...@froup.com wrote:
> >If the standard Twisted logging functions automatically constructed
> >LogMessage instances from dict instances, it should be easy enough for
> >future ILogObserver implementation
On 29 Nov, 06:44 pm, ddwigg...@advpubtech.com wrote:
>On 11/17/2011 3:26 PM, exar...@twistedmatrix.com wrote:
>>`msg` doesn't really care about what you give it. It doesn't support
>>the `format` keyword in any particular way. It's the job of a log
>>observer to handle that sort of thing. So it c
On 04:07 am, screwt...@froup.com wrote:
>On Tue, Nov 29, 2011 at 10:44:21AM -0800, Don Dwiggins wrote:
>>Looking at the source of log.py, I'm at a bit of a loss to reconcile
>>these two forces. Certainly, the two log observers implemented there
>>use textFromEventDict, but one could create a diffe
On Tue, Nov 29, 2011 at 10:44:21AM -0800, Don Dwiggins wrote:
> Looking at the source of log.py, I'm at a bit of a loss to reconcile
> these two forces. Certainly, the two log observers implemented there
> use textFromEventDict, but one could create a different observer that
> does things entir
On 11/17/2011 3:26 PM, exar...@twistedmatrix.com wrote:
> `msg` doesn't really care about what you give it. It doesn't support
> the `format` keyword in any particular way. It's the job of a log
> observer to handle that sort of thing. So it could certainly be
> documented, but don't mix things t
On 09:10 pm, kevin.h...@gmail.com wrote:
>On Wed, Nov 16, 2011 at 2:27 PM, Don Dwiggins
>wrote:
>>**
>>On 11/15/2011 8:57 AM, Christopher Armstrong wrote:
>>
>>If you pass a 'system' kwarg to log.msg then it will go in that field.
>>
>> log.msg("hi", system="stuff") results in [stuff] hi
>>
>>
>
On Wed, Nov 16, 2011 at 2:27 PM, Don Dwiggins wrote:
> **
> On 11/15/2011 8:57 AM, Christopher Armstrong wrote:
>
> If you pass a 'system' kwarg to log.msg then it will go in that field.
>
> log.msg("hi", system="stuff") results in [stuff] hi
>
>
> This triggered me to look further into what Log
On 11/15/2011 8:57 AM, Christopher Armstrong wrote:
If you pass a 'system' kwarg to log.msg then it will go in that field.
log.msg("hi", system="stuff") results in [stuff] hi
This triggered me to look further into what LogPublisher.msg does, since
I've long wanted to customize the format of
12 matches
Mail list logo
