Many zcml directives have a "for" attribute, which take an interface as argument. Absent-minded people like me sometimes happen to put a real class instead of an interface in the "for" attributes.

* On browser:page, one can put a real class with no error. Is it correct?
* On browser:containerViews, that lead to a non explicit error :
 Error object: list.index(x): x not in list

Is there a possibility to check this thing during startup, when zcml is parsed?
That would save time finding out what the real problem is.

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to