#34532: Overriding ModelForm default_renderer has no effect as forms api always
uses renderer from settings
----------------------------------+--------------------------------------
Reporter: Ryan Burt | Owner: nobody
Type: Bug | Status: closed
Component: Forms | Version: 4.2
Severity: Normal | Resolution: needsinfo
Keywords: default_renderer | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* cc: David Smith (added)
* status: new => closed
* resolution: => needsinfo
Comment:
Can you provide a sample project that reproduces the issue? How do you
initialize forms? Please reopen the ticket if you can provide more
details.
> or if the above code block could be restructured to preference
default_renderer if it is not none
Unfortunately not, the `renderer` explicitly passed in the arguments
should always be preferred as `default_renderer` is a fallback.
--
Ticket URL: <https://code.djangoproject.com/ticket/34532#comment:2>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187dff7285e-fe150ebe-8ffe-4388-b8c1-98f4ef1ac57d-000000%40eu-central-1.amazonses.com.
