Hi,
On Thu, Jun 13, 2013 at 6:41 PM, Facundo Batista
wrote:
> Mmm... which is the problem with doing:
>
> log.msg("Foo happened. Relevant information includes: "
> "bar=%s baz=%s boz=%s", bar, baz, boz)
>
> Is way more readable, and in the practice the code will just need to
> do som
On Thu, Jun 13, 2013 at 7:14 PM, Glyph wrote:
> For a long time, there's been consensus among at least a few core Twisted
> developers that log messages ought to be specified in terms of a format
> message and several relevant keyword arguments, so that tools can extract
> the values of the keywo
On Thu, Jun 13, 2013 at 5:14 PM, Glyph wrote:
> Hello everybody. Today I'd like to talk about everyone's favorite subsystem
> within Twisted: logging.
>
> There are a number of problems with Twisted's logging system.
I really need to get out of here and go to dinner, but I really
quickly wanted t
On Thu, Jun 13, 2013 at 5:14 PM, Glyph wrote:
>
> Hello everybody. Today I'd like to talk about everyone's favorite subsystem
> within Twisted: logging.
>
> There are a number of problems with Twisted's logging system.
Thanks for writing up this email. I'd like to help out with this effort.
> F
Hello everybody. Today I'd like to talk about everyone's favorite subsystem
within Twisted: logging.
There are a number of problems with Twisted's logging system.
The general theme of these problems is that Twisted log system was designed
with some intended use-cases in mind, but its implementa
