On Mar 6, 2011, at 8:07 AM, Martin Weissenboeck wrote:
> One more question:
> The validator IS_STRONG has the following error messages:
>
> "Minimum length is %s"
> "Maximum length is %s"
> "Must include at least %s of the following : %s"
> "May not contain any of the following: %s"
> "Must includ
One more question:
The validator IS_STRONG has the following error messages:
"Minimum length is %s"
"Maximum length is %s"
"Must include at least %s of the following : %s"
"May not contain any of the following: %s"
"Must include at least %s upper case"
"May not include any upper case letters"
"Mus
Ok, compatibility is a reason I understand.
You are right: if I make a decision, which error message would be
appropriate for each single field it works fine.
If there is a lot of fields with IS_INT_IN_RANGE requirements like T('enter
an integer between %(min)g and %(max)g') I will use an additio
On Mar 5, 2011, at 4:01 AM, Martin Weissenboeck wrote:
> This solution is not very beautiful, because I have to repeat the string
> 'fill this', but it works.
> It does not work for classes like IS_INT_IN_RANGE, because there is a lot of
> error messages, depending on the values:
>
> if
Some weeks ago there has been a discussion about this problem, but I did not
find any solution in the new version 1.93.2
Therefore: may I repeat a proposal?
>From the description of /gluon/validators.py:
Built-in validators have constructors that take the optional argument
error
message w
5 matches
Mail list logo
