#27039: ModelFields with 'default' value set and 'required'=False in form does not use default value -------------------------------------+------------------------------------- Reporter: Ivan Belokobylskiy | Owner: nobody Type: Bug | Status: closed Component: Forms | Version: 1.10 Severity: Release blocker | Resolution: fixed Keywords: default non- | Triage Stage: Accepted required modelform | Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Tim Graham): I'm doubtful that further complexity in this area is a good idea but this isn't a good place to discuss it. Design decisions are discussed on the DevelopersMailingList. Providing a patch to show your idea is feasible and wouldn't break backwards compatibility would help the discussion greatly. -- Ticket URL: <https://code.djangoproject.com/ticket/27039#comment:20> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/064.8aa361e3aa9316b04240d0a387c85376%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.