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 find any ready ones) > (e.g. IntRange(10,100)) Doesn't Int(min=10, max=99) work? > I'd have to polish those. And of course the IntRange validator is > trivial. I needed it anyway. > > While you are at it: I think the documentation about the "state" could > be improved. It's thrown around like it's self-explantory but the uses > had not been clear to me. That applies to the @validate docstring of > Pylons as well because it's useful to pass along a state (e.g. a > database/ORM object). Yeah... it's kind of vague. It makes sense in the context of something like Pylons, but otherwise it's very generic. There is a section in the docs: http://formencode.org/Validator.html#state -- I guess it lacks a good example, though. Is there a good example you can suggest? -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org : Write code, do good : http://topp.openplans.org/careers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
