[Zope] Re: filter messages at startup

[Chris McDonough]

I suppose a log call is fine.

I *really* like these messages, because they catch a lot of my own  
boneheaded security declaration errors.  But for ones that aren't  
actually "real" problems (like the ones shown by the OP), it would be  
nice to be able to filter them away at startup, especially when  
starting in the foreground or running "zopectl debug" or "zopectl  
test".  Making these into actual warnings.warn calls would let us do  
that with a warnfilter, but any other solution would be fine as well.

- C

On Jun 13, 2006, at 5:18 PM, Florent Guillaume wrote:

> Indeed they are logging.getLogger("Init") calls (from App/ 
> class_init.py).
> Why change that? They're perfectly fine in the event log.
>
> Florent
>
> On 13 Jun 2006, at 23:08, Chris McDonough wrote:
>
>>
>>>> Not out of the box.
>>
>> Egads, I think you're right.  These aren't actual warnings, are  
>> they?  They're log calls.  That should be changed.
>>
>> - C
>>
>>> [root at biow3 tests]# /zope/test/bin/zopectl debug
>>> Starting debugger (the name "app" is bound to the top-level Zope  
>>> object)
>>> 2006-06-13 13:48:34 WARNING Init Class
>>> Products.CMFCore.PortalContent.PortalContent has a security  
>>> declaration for
>>> nonexistent method 'manage_FTPget'
>>> 2006-06-13 13:48:34 WARNING Init Class
>>> Products.CMFCore.PortalContent.PortalContent has a security  
>>> declaration for
>>> nonexistent method 'manage_FTPget'
>
>
> -- 
> Florent Guillaume, Nuxeo (Paris, France)   Director of R&D
> +33 1 40 33 71 59   http://nuxeo.com   fg at nuxeo.com
>
>