id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
37315	Backport #36487 to 5.2/6.0, or document partial callback crash with robust=True	Bona Fide IT GmbH		"This is a follow-up to ticket #36487, which fixed an issue where `transaction.on_commit` error logging fails when using `functools.partial` with `robust=True`. 

The fix landed in Django 6.1, but we ran into this issue on Django 5.2 LTS, and I'd like to propose either a backport or a documentation fix for the `stable/5.2.x` and `stable/6.0.x` branches.

Currently in 5.2 and 6.0, `robust=True` does the opposite of what it promises for `partial` callbacks: the `except` clause that is supposed to swallow the error raises an `AttributeError` of its own (`'functools.partial' object has no attribute '__qualname__'`), turning a handled error into an unhandled one.

{{{
#!python
from functools import partial
from django.db import transaction

def boom(**kwargs):
    raise OSError(""broker is down"")

transaction.on_commit(partial(boom, pk=7), robust=True)
# AttributeError: 'functools.partial' object has no attribute '__qualname__'
}}}

This is particularly painful because it stays invisible until a failure actually happens in production, and the official 5.2/6.0 documentation explicitly recommends this exact combination. 

The docs for `on_commit()` recommend:
> ""Callbacks will not be passed any arguments, but you can bind them with `functools.partial()`""

And for `robust=True` they promise:
> ""All errors derived from Python's Exception class are caught and logged...""

Because 5.2 is an LTS release supported until April 2028, readers following the documentation will continue to hit this crash. Therefore, I'd like to propose two options for the triage team to consider:

'''Option 1: Code Backport (Preferred)'''
Backport the 2-line fix from #36487 to `stable/5.2.x` and `stable/6.0.x`. I understand the strict backport policy for extended support LTS releases (security/data-loss only). However, because the current behavior crashes a natively documented feature and turns handled errors into unhandled exceptions, an exception might be warranted.

'''Option 2: Documentation Warning (Fallback)'''
If a code backport is rejected under the backport policy, I propose adding a warning block to the 5.2 and 6.0 documentation for `on_commit`. The warning would clarify that `robust=True` crashes with `functools.partial` in these versions, and suggest the workaround (using a closure or manually setting `__qualname__` on the partial).

I am happy to prepare the patch for whichever option the team prefers!"	Bug	new	Database layer (models, ORM)	5.2	Normal			Bona Fide IT GmbH	Unreviewed	0	0	0	0	0	0