#36234: Restore single_object argument to LogEntry.objects.log_actions()
---------------------------------+------------------------------------
Reporter: Adam Johnson | Owner: (none)
Type: Bug | Status: new
Component: contrib.admin | Version: 5.1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by hesham hatem):
I'd like to help with this issue. From what I understand, the
single_object argument was accidentally removed from
LogEntry.objects.log_actions() in Django 5.1.7, causing backward
compatibility issues. Since this was removed in a bug fix release without
going through the proper deprecation process, we need to restore it in
Django 5.1 and properly deprecate it in Django 5.2.
I can work on a patch that:
1. Restores the single_object parameter to maintain backward compatibility
2. Adds a deprecation warning when it's used
3. Updates the documentation to indicate this parameter is deprecated
Would this approach be correct? Is there anything else I should consider
when implementing this fix?
--
Ticket URL: <https://code.djangoproject.com/ticket/36234#comment:3>
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 visit
https://groups.google.com/d/msgid/django-updates/010701956d0c4108-0b185cd5-e05a-4483-bd54-d5c2ead25139-000000%40eu-central-1.amazonses.com.
