#18212: GenericIPAddressField does not handle verbose_name and name args like
other
field types
-------------------------------------+-------------------------------------
Reporter: toofishes | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.4
(models, ORM) | Resolution: invalid
Severity: Normal | Triage Stage:
Keywords: fields | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by claudep):
* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
Nothing in the current documentation guarantees that the first argument to
any field constructor will be the verbose_name.
For example, GenericIPAddressField is documented as:
{{{
class GenericIPAddressField([protocol=both, unpack_ipv4=False,
**options])
}}}
verbose_name should always be used as a keyword parameter, like most other
field init parameters.
--
Ticket URL: <https://code.djangoproject.com/ticket/18212#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
