Adrian Holovaty wrote: > Ah, but we *will* have USStateField and USStateField field -- I just > haven't written those Field classes yet. :) >
Why not just have a CharField and a USState validator and an IPaddress4 validator. That way you have a USState validator to apply to other fields as well. You may well have a USState validator and an IsAllUpperCase validator. You could then combine the USState validator with the IsAllUpperCase validator without creating any new fields. You could even use those validators in different combinations with other validators to achieve different functionality, again without creating any new fields or even validators at all. Again a trivial (and in this case possibly stupid) example, but I think the principle is sound. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
