Evan Simpson said:
> Tim Hicks wrote:
>> Given a call signature like:
>> def method(self, *args, **kw)
>> In this way, mapply.py seems to ignore the fact that I want my method
>> to accept an arbitrary number of arguments (line 69).
> When mapply was written, its only purpose was to map explicit method
> parameters to request variables. There was no concept of RPC of any
> kind, so neither '*args' nor '**kwargs' had any kind of sensible
> So, yes, mapply does ignore what you want :-)
> Unfortunately, given the way that XML-RPC and WebDAV have been piled on
> top of the initial implementation, I'm not sure how this could be fixed
> properly in Zope 2.x.
> Evan @ 4-am
thanks for at least confirming my fears. I've got a workaround going now;
albeit with slightly hobbled functionality.
As is the standard cry at these times - 'will this be fixed in Zope3?'
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -