On Mar 31, 2012, at 6:10 PM, Brian Warner wrote:
> On 3/30/12 5:49 PM, Glyph wrote:
>
>>> http://foolscap.lothar.com/docs/logging.html has details.
>>
>> Indeed, Foolscap has informed many of my future wishes for Twisted
>> logging, especially its incident reporting and logport features. (I
>>
On 3/30/12 5:49 PM, Glyph wrote:
>> http://foolscap.lothar.com/docs/logging.html has details.
>
> Indeed, Foolscap has informed many of my future wishes for Twisted
> logging, especially its incident reporting and logport features. (I
> wasn't aware of UMIDs but I have independently invented the
On Mar 30, 2012, at 3:23 PM, Brian Warner wrote:
> On 3/25/12 7:11 PM, Glyph wrote:
>
>> I'm going to try to get started on record my desired behavior for
>> logging as tickets soon though, so Twisted can at least have some really
>> good logging tools /eventually/.
>
> While you're thinking
On 3/25/12 7:11 PM, Glyph wrote:
> I'm going to try to get started on record my desired behavior for
> logging as tickets soon though, so Twisted can at least have some really
> good logging tools /eventually/.
While you're thinking about this space, I'll plug the logging tools I
built into Foo
On Mar 26, 2012, at 10:38 AM, exar...@twistedmatrix.com wrote:
> I agree with just about everything here, except I think we should be
> able to do better than the `format="opaque string"ยด part.
In principle I agree, but I'm not sure about how to do that _exactly now_.
Whereas today, immediate
On 02:11 am, gl...@twistedmatrix.com wrote:
>Right now, we have a pretty bad logging idiom. All over Twisted,
>you'll find stuff like this:
>
>log.msg("twistd %s (%s %s) starting up." % (copyright.version,
>sys.executable,
>runtime.shortPythonVersion())
