#11716: Various methods in django.db.models.fields don't wrap ValueErrors and
allow
them to escape
---------------------------------------------------+------------------------
Reporter: Leo | Owner: Leo
Status: assigned | Milestone: 1.2
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by Leo):
* needs_better_patch: 1 => 0
Comment:
Ok, I've updated the patch. There were a few more details involved here:
* several functions in !BooleanField would accept a value of None
silently, that's no longer the case - this is backed up by the thinking in
#5563
* !IntegerField's default error message had a typo in it - `'invalid':
_("This value must be a float.")` - it's been changed to read correctly -
`This value must be an integer.`
Please let me know if there are any more issues that need to be resolved.
I'd really love to get this into 1.2.
--
Ticket URL: <http://code.djangoproject.com/ticket/11716#comment:10>
Django <http://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-upda...@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.
