#22716: The unique error message uses incorrect grammar
-------------------------------+--------------------------------------
Reporter: jdufresne | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.6
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by jdufresne):
Thanks for the link to the commit. That was informative.
> I think it's unlikely we can change it due to backwards compatibility.
Compatibility with what? Is this really a case of backwards compatibility?
This isn't an API, logic, or behavior. This is incorrect capitalization of
words. I'm sorry, but I really don't see how backwards compatibility plays
a part here. Would the same be said for a spelling mistake in the same
sentence? That's what this looks like to me.
If I were to draft a pull request that, all else being equal, used
`field.verbose_name` instead of `capfirst(field.verbose_name)` when
putting field name in a sentence would it have a real chance of being
accepted? If it is required, I'd even consider coding in a deprecation
path that simply warns capitalization will change in a future release.
--
Ticket URL: <https://code.djangoproject.com/ticket/22716#comment:4>
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/067.1ce00fd27565c2b87e0f56c908fb8928%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
