Hi,
The z3c.form doctests make it look like raising zope.interface.Invalid()
would be an acceptable thing for a validator to do. It also makes it
look like the argument passed to the Invalid() constructor is a string
that would be displayed as an error message.
However, when I do this (in a
On Friday 26 February 2010, Martin Aspeli wrote:
The z3c.form doctests make it look like raising zope.interface.Invalid()
would be an acceptable thing for a validator to do. It also makes it
look like the argument passed to the Invalid() constructor is a string
that would be displayed as an
Stephan Richter wrote:
On Friday 26 February 2010, Martin Aspeli wrote:
The z3c.form doctests make it look like raising zope.interface.Invalid()
would be an acceptable thing for a validator to do. It also makes it
look like the argument passed to the Invalid() constructor is a string
that
On 02/26/2010 04:23 PM, Martin Aspeli wrote:
Stephan Richter wrote:
On Friday 26 February 2010, Martin Aspeli wrote:
The z3c.form doctests make it look like raising zope.interface.Invalid()
would be an acceptable thing for a validator to do. It also makes it
look like the argument passed to
On Friday 26 February 2010, Martin Aspeli wrote:
Feel free to fix the bug with a test. You can also release a new z3c.form
version if you like. I can give you access
Fixed.
I also added the behaviour to not render anything for a non-200 request.
My PyPI username is optilude if you'd
