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
27312	Checking raw argument to prevent signals from executing during fixture loading isn't DRY	Álex Córcoles	nobody	"We have some signals that create information when some models are added/updated which should not be run when loading fixtures.

We have had to use the raw argument to disable each signal when fixtures are being loaded, and it works, but it is not ideal as we have to repeat the same bit of code in each affected signal (basically ""if raw: return""), which is duplicated code (which we do not like) and code we have to test (which adds overhead- esp. as the code contains a conditional and messes with coverage).

I think it would be better if you could state that you only want to connect your signal for non-fixture operations- this way it would be 100% declarative and not require any testing).

Other alternatives could be provided as not running signals on fixtures by default, which I think it's a nicer default, but might be controversial.
"	Cleanup/optimization	closed	Core (Other)	1.10	Normal	needsinfo	fixtures signals		Unreviewed	0	0	0	0	0	0