On Jun 9, 2008, at 10:10 AM, pihentagy wrote: > > Hi all! > > In the docs here: > http://www.djangoproject.com/documentation/model-api/#verbose-field-names > > Each field type, except for ForeignKey, ManyToManyField and > OneToOneField, takes an optional first positional argument — a verbose > name. If the verbose name isn’t given, Django will automatically > create it using the field’s attribute name, converting underscores to > spaces. > > Is there a good reason to handle the verbose name differently in these > cases? (Is there a chance it will behave as expected, like other field > types?)
It’s the only way to make it required. When defining methods (including __init__), all required arguments must be listed first. Otherwise it’s ambiguous. -- Peter of the Norse --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
