"Geir Magnusson Jr." <[EMAIL PROTECTED]> writes:
> > I have added support to ASTIdentifier by adding a PythonExecutor that will
> > try to resolve reference from anything that subclasses PyObject. This is a
> > pretty clean fit I think and doesn't require much code. I was about to
> > extend ASTMethod to handle the method case, but here is the thing. I don't
> > want to create a solid dependency on Jython in the Velocity codebase. What
> > I would like from people are ideas about how to extend the AbstractExecutor
> > notion to be more like plugable directive and then extend this notion to
> > the AST{Identifier, Method, Reference?}
>
> If you can do it in the AST, why not just make a conventionally
> introspectable wrapper class for the python stuff...? Then you can drop
> that right into the context, and no one is the wiser....
This is definitely the best way to handle this. Your wrapper could go
into our contrib/optional section.
