> Well, surprise is in the eye of the participant. As noted above, it > would be surprising to a lot of us if it did pick up the attributes > because it removes control from the user. The current behaviour isn't > illogical.
Oh, I wasn't suggesting that the user shouldn't be able to override those values, I was only talking about what the default behavior should be if the user doesn't specify anything. If the user instantiates a form field, and doesn't specify what 'required' should be (and the field itself doesn't set this value), it just seems far more natural to pick up the value the user already specified in the model, rather than arbitrarily choosing 'True'. Part of the reason I think this represents a common use case is that these attributes seem fairly orthogonal to the purposes of validating/ rendering that fields and widgets are used for. That is, I wouldn't imagine that it's common that your choice of which field or widget to use to represent a model field will affect whether or not that field is required, say. Of course, my experience is limited. I don't know enough yet to suggest how this would be implemented, I just wanted to throw the idea out there. But unless there's a groundswell of support for my position, I guess I'll just file a documentation ticket. Cheers, Kevin --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
