Philipp von Weitershausen wrote at 2006-5-23 17:02 +0200: > ... >callable() isn't even deprecated yet, so if it solves our problem, we >can use it IMO. Note that Zope 3 deliberately doesn't use it because of >the proxy problem. Zope 2 works around that by stripping >proxies/wrappers first (ob.aq_base). Perhaps Zope3 should do that as >well. Would callable(removeAllProxies(obj)) be harmful in any way if you >end up calling the proxied obj() anyway?
At least earlier, "callable" had a problem: some objects where apparently "callable" but calling them resulted in "AttributeError: __call__". That's why "cDocumentTemplate" grew a "safe_callable". -- Dieter _______________________________________________ Zope3-dev mailing list Zope3email@example.com Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com