<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jun 20, 2013, at 4:03 PM, <a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On 18 Jun, 08:58 pm,<span class="Apple-converted-space"> </span><a href="mailto:termim@gmail.com">termim@gmail.com</a><span class="Apple-converted-space"> </span>wrote:<br><blockquote type="cite">From the practical POV the most welcomed first step in updating the Twisted<br>log system would be introduction of ready made log levels (with an ability<br>to filter on them in observers), fix of logPrefix thing and somewhat<br>extended set of available observers (syslog, email, socket, etc.)<br>Everything else could wait more detailed design etc.<br></blockquote><br>Is there an obstacle preventing this from being done with twisted.python.log?<br><br>A completely new system written from scratch from the ground up might be great, but it doesn't seem necessary for something as simple as log level support.<br><br>Jean-Paul</div></blockquote><br></div><div dir="auto">Nope. Anyone who wants to start adding log levels to any existing messages is welcome to do so. There's no particular conflict with the new system, either; more information in log messages will just be even easier to utilize with some of its improvements.</div><div dir="auto"><br></div><div dir="auto">-glyph</div><div><br></div></body></html>