#12467: More helpful error message when loading fixture with invalid date
--------------------------------------+------------------------------------
Reporter: knutin | Owner: raulcd
Type: New feature | Status: assigned
Component: Core (Serialization) | Version: SVN
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by charettes):
Replying to [comment:5 julien]:
> The patch looks good. While we're at it, we should also do the same for
`DateField`'s "invalid_date" and `DateTimeField`'s "invalid" messages. See
amended patch attached.
That would be a great addition. I have one question concerning the
attached patch.
How are the ValueError risen by {{{datetime.date}}} calls supposed to be
translated? I see you're calling {{{_(str(e))}}} before formating the
{{{invalid_date}}} message but I can't find where django is supposed to
catch i.e. {{{_('month must be in 1..12')}}} when {{{makemessages}}} logic
is invoked.
--
Ticket URL: <https://code.djangoproject.com/ticket/12467#comment:6>
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.
