#18212: GenericIPAddressField does not handle verbose_name and name args like
other
field types
-------------------------------------+-------------------------------------
Reporter: toofishes | Owner: Claude
Type: Bug | Paroz <claude@…>
Component: Database layer | Status: closed
(models, ORM) | Version: 1.4
Severity: Release blocker | Resolution: fixed
Keywords: fields | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz <claude@…>):
In [92f7af3c36ec62e0b55c69ae8e359e53c8cfec15]:
{{{
#!CommitTicketReference repository=""
revision="92f7af3c36ec62e0b55c69ae8e359e53c8cfec15"
[1.4.x] Fixed #18212 -- Standardized arguments of GenericIPAddressField
Unlike other model fields, the newly introduced (1.4)
GenericIPAddressField did not accept verbose_name and name as the
first positional arguments. This commit fixes it.
Thanks Dan McGee for the report and the patch.
Backport of 306d34873cff2 from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/18212#comment:7>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
