On 9/16/12 07:28 , Marius Gedminas wrote:
On Fri, Sep 14, 2012 at 01:44:30PM +0200, Jan-Wijbrand Kolman wrote:
The reason I came across this issue is trying to improve the test
coverage of the application I'm building somewhat closer to 100% and
found that the form actions implementation
On 9/16/12 09:38 , Wichert Akkerman wrote:
On Sep 16, 2012, at 07:28, Marius Gedminas mar...@gedmin.as wrote:
On Fri, Sep 14, 2012 at 01:44:30PM +0200, Jan-Wijbrand Kolman wrote:
After years and years of heavily using zope.formlib it suddenly struck
me that the zope.formlib.form.action
On Sep 16, 2012, at 07:28, Marius Gedminas mar...@gedmin.as wrote:
On Fri, Sep 14, 2012 at 01:44:30PM +0200, Jan-Wijbrand Kolman wrote:
After years and years of heavily using zope.formlib it suddenly struck
me that the zope.formlib.form.action decorator returns an Action()
object instead of
On Fri, Sep 14, 2012 at 01:44:30PM +0200, Jan-Wijbrand Kolman wrote:
After years and years of heavily using zope.formlib it suddenly struck
me that the zope.formlib.form.action decorator returns an Action()
object instead of the decorated function (this action object is also
added to the
Hi,
After years and years of heavily using zope.formlib it suddenly struck
me that the zope.formlib.form.action decorator returns an Action()
object instead of the decorated function (this action object is also
added to the form's actions sequence as a side effect of the decorator).
I know
