[Zope3-checkins] CVS: Zope3/lib/python/Zope/Configuration - meta.py:1.9
R. David Murray
bitz@bitdance.com
Wed, 18 Sep 2002 00:24:38 -0400
Update of /cvs-repository/Zope3/lib/python/Zope/Configuration
In directory cvs.zope.org:/tmp/cvs-serv29183
Modified Files:
meta.py
Log Message:
Update docstring of registersub to match previous refactoring.
Note that the bit about the methods being looked up on the
ISubdirectiveHandler returned by the INonEmptyDirective of the
parent (sub)directive is logical speculation on my part.
The other possability is that it is always looked up on
the one associated with the top level directive. If I've gotten
it wrong either someone will correct me or I'll figure it out as I
get further into the code and fix it myself.
=== Zope3/lib/python/Zope/Configuration/meta.py 1.8 => 1.9 ===
--- Zope3/lib/python/Zope/Configuration/meta.py:1.8 Tue Sep 17 23:49:52 2002
+++ Zope3/lib/python/Zope/Configuration/meta.py Wed Sep 18 00:24:37 2002
@@ -62,10 +62,12 @@
name string.
The handler is not passed as it normally is for top-level
- directives. Rather, the handler is looked up as an attribute of
- the top-level directive object using the name string that is the
- second element in the name tuple. An optional handler attribute
- can be used to specify the method to be used.
+ directives. Rather, the handler will be looked up as an attribute
+ of the ISubdirectiveHandler returned by INonEmptyDirective whose
+ associated registry we have been passed. The string to be
+ looked up is set to the second element of the name tuple, unless
+ the optional handler attribute is used to provide the lookup
+ string explicitly.
Subdirectives may have subdirectives. The subdirectives will be
registered in a registry that is stored with the containing
@@ -78,6 +80,8 @@
subdirs = {}
directives[name] = subdirs, handler_method
return subdirs
+
+
def _exe(callable, subs, context, kw):
r = callable(context, **kw)