Re: [Django] #34802: django.contrib.admin.actions.delete_selected() should return number of rows deleted via ModelAdmin.delete_queryset() (was: django.contrib.admin.actions.delete_selected(): return number of rows deleted via ModelAdmin.delete_queryset())

[Django]

#34802: django.contrib.admin.actions.delete_selected() should return number of rows
deleted via ModelAdmin.delete_queryset()
---------------------------------+--------------------------------------
Reporter: Wicher Minnaard | Owner: nobody
Type: New feature | Status: closed
Component: contrib.admin | Version: 4.2
Severity: Normal | Resolution: wontfix
Keywords: | 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):

* status: new => closed
* type: Uncategorized => New feature
* has_patch: 1 => 0
* resolution: => wontfix

Comment:

Thanks for the ticket, however `delete_queryset()` was added to change a
deletion process not to change a list of objects to be deleted (as
documented), e.g. use `Model.delete()` instead of a bulk deletion. IMO,
any implicit queryset modification can be confusing for users and will
brake other things as `log_deletion()`. I have doubts the described use
case should be supported.

Please first start a discussion on the DevelopersMailingList, where you'll
reach a wider audience and see what other think, and
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features follow the guidelines with regards to
requesting features].

--
Ticket URL: <https://code.djangoproject.com/ticket/34802#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.