#29735: MRO of DeleteView need to be changed.
-------------------------------------+-------------------------------------
Reporter: seokhun kim | Owner: seokhun
Type: | kim
Cleanup/optimization | Status: closed
Component: Generic views | Version: master
Severity: Normal | Resolution: wontfix
Keywords: deletemixin, | Triage Stage:
basedeleteview, deleteview, | Unreviewed
generic view |
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: assigned => closed
* resolution: => wontfix
Comment:
Replying to [comment:3 Simon Charette]:
> I haven't investigated this in details but I'm a bit worried about
changing the MRO and moving the methods off `DeleteMixin` for the sake of
purity. Don't get me wrong, I think that these changes would make sense if
we were to start from scratch but in this case I feel breakage risks
outweigh the benefits.
This seems right. I think for the breaking-change we have to close this as
`wontfix`.
I'm not 100% on that. I've opened a [https://groups.google.com/d/topic
/django-developers/R_pgZTMc3oA/discussion django-developers thread] asking
for other opinions. Very happy to re-open if we think this is something we
can do.
--
Ticket URL: <https://code.djangoproject.com/ticket/29735#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.a496c8da8076336539aa3ceaafe5a252%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
