#8104: IntegerField max_value & min_value errors require a %s
------------------------------------------------------+---------------------
Reporter: Chris Jones <ch...@brack3t.com> | Owner: nobody
Status: closed | Milestone:
Component: Forms | Version:
Resolution: duplicate | Keywords:
IntegerField max_value min_value TypeError
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------------------------+---------------------
Changes (by gabrielhurley):
* status: new => closed
* resolution: => duplicate
Comment:
As adamv points out, the design decision seems to have been made (by
standardizing the use of mapping keys for 1.3), so that would make this a
docs ticket. And since adamv was kind enough to create #14708 with a
complete patch (looks complete at least from a cursory review), I'm
closing this as a duplicate.
--
Ticket URL: <http://code.djangoproject.com/ticket/8104#comment:5>
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.
