>> but those min max constraints are so common? why not include >> it? > > Because "common" is different for any given user and/or site. > I think *I've* only written a single form with min/max > validation, FWIW. Designing a framework is hard; you've got to > search for things that are as close to truly universal as > possible.
This is especially the case with Django...writing a simple min/max validator is trivial to do and Django makes it easy to use any set of validators you want on your fields. That said, I don't see a great reason not to include a min_length and max_length validator in Django's standard toolkit of validators as I've seen this question pop up a couple other times on the list and have written them myself in the past. > Otherwise you end up including every little pet feature that > someone asks for, and that's known as "PHP". but pythonistas can at least sort them into namespaces ;) -tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
