#34531: Rendering form throws deprecation warning
-------------------------------+--------------------------------------
Reporter: Petr Dlouhý | Owner: nobody
Type: Uncategorized | Status: closed
Component: Forms | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:2 Petr Dlouhý]:
> Even now when I read the Forms section I would be confused what should I
do if I haven't read your comment.
This note is crucial:
> ''"In order to smooth adoption of the new `<div>` output style, two
transitional form renderer classes are available:
`django.forms.renderers.DjangoDivFormRenderer` and
`django.forms.renderers.Jinja2DivFormRenderer`, for the Django and Jinja2
template backends respectively. You can apply one of these via the
`FORM_RENDERER` setting. For example:"''
> {{{
> FORM_RENDERER = "django.forms.renderers.DjangoDivFormRenderer"
> }}}
> ''"Once the <div> output style is the default, from Django 5.0, these
transitional renderers will be deprecated, for removal in Django 6.0. The
`FORM_RENDERER` declaration can be removed at that time."''
I'm not sure how it could be clearer.
--
Ticket URL: <https://code.djangoproject.com/ticket/34531#comment:3>
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/01070187e0c8689b-56331a44-5bc9-4c18-b081-f32e3f0bb717-000000%40eu-central-1.amazonses.com.
