#24756: Unexpected behavior of ModelForm.save for fields with blank=False and
overridden required attribute
-------------------------------------+-------------------------------------
Reporter: bboogaard | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: 1.8
Severity: Release blocker | Resolution:
Keywords: forms models save | Triage Stage:
blank required | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by bboogaard):
All right, if it was an unintended effect of previous versions, I'll
simply change my model field declarations and code logic. I thought the
override was supposed to work the way I described (i.e. in principle
required, but for some form classes not required).
--
Ticket URL: <https://code.djangoproject.com/ticket/24756#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.83b0c648a6a014c54ecd719c10f5590d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
