#33263: DeleteView in Django4.0 does not call .delete() method
-------------------------------------+------------------------------------
Reporter: Eugene Prikazchikov | Owner: nobody
Type: Bug | Status: new
Component: Generic views | Version: 4.0
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Comment (by Eugene Prikazchikov):
By deprecation process I meant that initially behavior is kept the same,
but the warning is emitted in runtime. In our case, when `.delete` method
is reached during `POST` request, we could emit a warning like "the logic
from .delete() method must be moved to .form_delete()". Thus, people
should have enough time to update their code.
And then in one of following releases we change the behavior. Like
described here - https://docs.djangoproject.com/en/3.2/howto/upgrade-
version/#resolving-deprecation-warnings
Though perhaps a note in **backwards incompatible changes** would be
enough (like https://docs.djangoproject.com/en/3.2/releases/1.11
/#backwards-incompatible-1-11)
--
Ticket URL: <https://code.djangoproject.com/ticket/33263#comment:6>
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/066.f65c5abf368f20fe2d9156378294697d%40djangoproject.com.