Hi @all, On Tuesday 12 August 2014 11:18:31 Glyph Lefkowitz wrote: > 2- I'll create t.p.logger._syslog > 3- I''ll patch t.p.syslog to use t.p.logger._syslog While writing 2, I found that
1- t.p.logger.LogLevel implements a mapping between syslog priorities and loglevels. 2- there's a private method which actually which doesn't seem to work as expected (priorities order is reversed): * LogLevel._priorityForLevel(LogLevel.debug) == 0 * should be 7 3- To have a correct mapping we should add `kern` even if probably it's not a value which fits to a python application. 4- There's an old closed ticket on that, but it doesn't say anything about loglevels but only an interesting discussion about NamedConstants Q1- Should we implement a priority mapping in LogLevel? Q2- Should we fix that method and make it public? Thx + Peace, R: -- Roberto Polli Community Manager Babel - a business unit of Par-Tec S.p.A. - http://www.babel.it T: +39.06.9826.9651 M: +39.340.652.2736 F: +39.06.9826.9680 P.zza S.Benedetto da Norcia, 33 - 00040 Pomezia (Roma) _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
