That fields accepts `model class` as first argument which is more important then `verbose_name` in this case.
On Jun 9, 8:10 pm, pihentagy <[EMAIL PROTECTED]> wrote: > Hi all! > > In the docs > here:http://www.djangoproject.com/documentation/model-api/#verbose-field-n... > > 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?) > > thanks > Gergo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---

