Skip to content

Commit bebe7e7

Browse files
d-w-mooretrel
authored andcommitted
[#338] clarify Python RE Plugin limitations
1 parent d53ebd9 commit bebe7e7

1 file changed

Lines changed: 9 additions & 0 deletions

File tree

README.rst

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -600,6 +600,15 @@ anticipate these and prefer to catch them as exceptions, we can do it this way::
600600
exit(1)
601601
print('Rule execution succeeded!')
602602

603+
Finally, keep in mind that rule code submitted through an :code:`irods.rule.Rule` object is processed by the
604+
exec_rule_text function in the targeted plugin instance. This may be a limitation for plugins not equipped to
605+
handle rule code in this way. In a sort of middle-ground case, the iRODS Python Rule Engine Plugin is not
606+
currently able to handle simple rule calls and the manipulation of iRODS core primitives (like simple parameter
607+
passing and variable expansion') as flexibly as the iRODS Rule Language.
608+
609+
Also, core.py rules may not be run directly (as is also true with :code:`irule`) by other than a rodsadmin user
610+
pending the resolution of `this issue <https://github.com/irods/irods_rule_engine_plugin_python/issues/105>`_.
611+
603612

604613
General queries
605614
---------------

0 commit comments

Comments
 (0)