#28009: Changes to models.CharField and forms.CharField impact subclasses as
well
-------------------------------------+-------------------------------------
Reporter: Matt | Owner: Matt Braymer-Hayes
Braymer-Hayes |
Type: | Status: assigned
Cleanup/optimization |
Component: | Version: 1.11
Documentation |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Hi folks, question: Do the changes made in #4136 also impact
`models.CharField` subclasses (`CommaSeparatedIntegerField`, `EmailField`,
`SlugField`, and `URLField`) and `forms.CharField` subclasses
(`RegexField`, `EmailField`, `URLField`, `GenericIPAddressField`,
`SlugField`, and `UUIDField`)? Based on my review of the code they do,
though I may be missing something. If they are, the docstrings and
documentation for each of the `forms.CharField` subclasses should be
updated. Additionally, the release notes should mention the other fields
impacted. I'm happy to make a PR, if this is the case.
--
Ticket URL: <https://code.djangoproject.com/ticket/28009>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.c9833fcfe3593232fe465927007fa60c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
