A pre/post batch_delete signal would be useful for the usage you describe.
There would likely be confusion with its usage because unlike post_delete,
the batch_delete signals would not be able to provide actual records. The
best it could do would be to provide the queryset and the deletion count on
Hello,
django-treebeard [1] has an optimized batch deletion for its models. [2]
The main reason is because post_delete signals are called for each
objects. And custom deletion in treebeard can be done in batch.
I was reading Django's code [3] and it looks like there's no way to hook
into _ra
