Tres Seaver wrote at 2005-10-16 14:22 -0400:
> ...
>> Probably, because they can bind the DTML namespace...
>
>I knew that they *could* bind it; it just don't understand why anyone
>would *want* that feature, given the availability of the other,
>non-ambiguous bindings.
I know that I used it inte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dieter Maurer wrote:
> Tres Seaver wrote at 2005-10-11 08:58 -0400:
>
>>...
>>'call_with_ns' should be invoked only for objects with either a
>>'__render_with_namespace__' attribute (PythonScripts fit here) or those
>>with 'isDocTemp' true. Its only
Tres Seaver wrote at 2005-10-11 08:58 -0400:
> ...
>'call_with_ns' should be invoked only for objects with either a
>'__render_with_namespace__' attribute (PythonScripts fit here) or those
>with 'isDocTemp' true. Its only real purpose is to set up the namespace
>before calling a DTMLMethod; I don
On Tue, Oct 11, 2005 at 08:58:08AM -0400, Tres Seaver wrote:
| 'call_with_ns' should be invoked only for objects with either a
| '__render_with_namespace__' attribute (PythonScripts fit here) or those
| with 'isDocTemp' true. Its only real purpose is to set up the namespace
| before calling a DTML
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidnei da Silva wrote:
> (sorry for the cross-post)
>
> I'm currently facing an issue that seems to be a result of a bad
> interaction between CMF, TALES and Restricted Python.
>
> The issue currently happens when:
>
> 1. A TALES 'Path Expression