iain duncan wrote:
On Wed, 2007-17-10 at 13:20 -0500, Ian Bicking wrote:
FormEncode is overdue for a release, but before that a request: there
has been some mention that FormEncode should ship more useful form
validators. For instance, FieldsMatch is an example of something
currently
On Thu, Oct 18, 2007 at 10:28:52PM -0400, Yannick Gingras wrote:
Christoph Haas [EMAIL PROTECTED] writes:
I could contribute validators for:
- valid IPv4 network/address specifications
(e.g. 10.0.0.0/8 or 192.168.25.1 but not 1.2.3.4/123)
Here is what I use for IPv4 addr ranges:
On Wed, 2007-17-10 at 13:20 -0500, Ian Bicking wrote:
FormEncode is overdue for a release, but before that a request: there
has been some mention that FormEncode should ship more useful form
validators. For instance, FieldsMatch is an example of something
currently shipped, but about the
Christoph Haas [EMAIL PROTECTED] writes:
I could contribute validators for:
- valid IPv4 network/address specifications
(e.g. 10.0.0.0/8 or 192.168.25.1 but not 1.2.3.4/123)
Here is what I use for IPv4 addr ranges:
from formencode import validators
import iplib
class
FormEncode is overdue for a release, but before that a request: there
has been some mention that FormEncode should ship more useful form
validators. For instance, FieldsMatch is an example of something
currently shipped, but about the only example. Other examples would be
helpful. Probably
On Wed, Oct 17, 2007 at 01:20:07PM -0500, Ian Bicking wrote:
FormEncode is overdue for a release, but before that a request: there
has been some mention that FormEncode should ship more useful form
validators. For instance, FieldsMatch is an example of something
currently shipped, but
Christoph Haas wrote:
I could contribute validators for:
- valid IPv4 network/address specifications
(e.g. 10.0.0.0/8 or 192.168.25.1 but not 1.2.3.4/123)
- valid hardware (MAC) address
(e.g. 01:51:a5:92:be:08)
Those would be useful, I think.
- range of integers (strange I didn't
