#24376: UUIDField doesn't take a verbose_name positional arg
----------------------------------------------+-----------------------
Reporter: yoyoma | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer (models, ORM) | Version: 1.8alpha1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
----------------------------------------------+-----------------------
Looking at
https://github.com/django/django/blob/master/django/db/models/fields/__init__.py#L2372,
{{{UUIDField}}} doesn't take a positional argument, which is inconsistent
with the behavior of other fields (the exception being relationship
fields). Since {{{UUIDField}}} will surely be used for more than just a
primary key replacement in some cases, it might be worth preserving this
consistency. If you core devs are ok with this, I'll make a patch.
Thoughts?
--
Ticket URL: <https://code.djangoproject.com/ticket/24376>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.8125cc7f52feef289bbb9b4dc3a582f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
