#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 Petr Dlouhý):
Hi Natalia,
thank you very much for your comment.
This clears things up. At the same time I am still a bit confused about
what is the deprecation message saying regarding this case.
I confess that I didn't read the whole release notes but only searched for
`default.html` keyword which found me one paragraph in the Miscellaneous
section which didn't help me much.
Even now when I read the Forms section I would be confused what should I
do if I haven't read your comment.
Also it is very hard to find the exact place in the template where the `{{
form }}` tag does occur since the deprecation message doesn't mention
anything about the template. I had to use `pudb` very extensively to learn
what is happening.
I suggest at least adding some more explicit info in the release notes
regarding this case.
If you are interested, I could try to formulate something.
--
Ticket URL: <https://code.djangoproject.com/ticket/34531#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/01070187e0b6fd0d-b5d23d5b-26c4-4b7e-bf56-d71bf54d3a83-000000%40eu-central-1.amazonses.com.
