On 12-08-20 5:52 PM, Hartmut Goebel wrote: > Am 20.08.2012 04:00, schrieb Francois Mikus: >> Answering myself is strange but hey, I am confused. > Please do not spent time analysing the logging. I've already done quite > some work on this. > > I have an idea (and a draft implementation) on how to switch to the > standard Python logging modules. This would solve many of the problems > you found. Unfortunately my spare time is rare currently and I had to > eliminate all usage of logger.log() first, as this conflicts with the > standard logger. > > I've just published pull-request #532 for eliminating .log(). If this is > accepted and Jenkins does not show up errors, I'll continue with the new > logging module. > > So please be patient just a few more days :-) > I saw what you just updated.
I suggest we merge your changes and I will resolve the conflicts from my changes and we can then merge it all. I have updated a *lot* of messages, levels, typos, comments and print to logger.xxx conversions. At this point there is only a couple of files in conflict it should be easy to resolve. Nap needs to review and accept the changes. You can take a look at my pull request as well. You will see there is not much in conflict. You are doing great work. I understand where you are going, but we need to get things sorted before continuing. I have put any more changes related logging on hold. Thank you, X ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
