[gnue] r8605 - in trunk/gnue-common/src: logic/adapters rpc/drivers utils

[reinhard]

Author: reinhard
Date: 2006-08-23 01:55:25 -0500 (Wed, 23 Aug 2006)
New Revision: 8605

Modified:
   trunk/gnue-common/src/logic/adapters/Base.py
   trunk/gnue-common/src/rpc/drivers/Base.py
   trunk/gnue-common/src/utils/tree.py
Log:
More epydoc fixes.


Modified: trunk/gnue-common/src/logic/adapters/Base.py
===================================================================
--- trunk/gnue-common/src/logic/adapters/Base.py        2006-08-22 19:56:22 UTC 
(rev 8604)
+++ trunk/gnue-common/src/logic/adapters/Base.py        2006-08-23 06:55:25 UTC 
(rev 8605)
@@ -29,7 +29,7 @@
 
 Language adapters are python modules that allow external, user provided code in
 a given language to be executed within Python. In GNU Enterprise, language
-adapters are used to execute L{usercode.action} actions, L{GTrigger.GTrigger}
+adapters are used to execute L{usercode.GAction} actions, L{GTrigger.GTrigger}
 triggers, and server side methods in GNUe-AppServer.
 
 Each language adapter implements this feature for a specific language. An

Modified: trunk/gnue-common/src/rpc/drivers/Base.py
===================================================================
--- trunk/gnue-common/src/rpc/drivers/Base.py   2006-08-22 19:56:22 UTC (rev 
8604)
+++ trunk/gnue-common/src/rpc/drivers/Base.py   2006-08-23 06:55:25 UTC (rev 
8605)
@@ -239,7 +239,7 @@
 
     @param method: name of the method to call
     @param args: tuple with all positional arguments
-    @param kwargs: dictionary with all keyword arguments
+    @param params: dictionary with all keyword arguments
 
     @return: result of the remote procedure call
     """

Modified: trunk/gnue-common/src/utils/tree.py
===================================================================
--- trunk/gnue-common/src/utils/tree.py 2006-08-22 19:56:22 UTC (rev 8604)
+++ trunk/gnue-common/src/utils/tree.py 2006-08-23 06:55:25 UTC (rev 8605)
@@ -697,7 +697,7 @@
     C{str}, or C{int}, but they can also be subclasses of L{NamedNode}. In this
     case, both C{my_node['my_attr'] = other_node} and
     C{my_node['my_attr'] = 'other_node_name'} are valid, and will cause
-    C{my_node['my_attr'] to evaluate to other_node, provided that other_node
+    C{my_node['my_attr']} to evaluate to other_node, provided that other_node
     has a name of 'other_node_name', both my_node and other_node are in the
     same tree, and the type of other_node is registered in the root node's
     C{_node_dicts_} list.