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
8077	Add ability to disable signals one a per-object-per-event basis.	brooks.travis@…	nobody	"Right now, built-in signals like pre_save and post_save are triggered for all models every time a new or existing instance is saved to the database. I would propose adding the capability to granularly disable any built-in signals on a per-event basis. Here's an example syntax:


{{{
>>>MyModel(name='John Doe', disabled_signals=['post_save'])
}}}


You should be able to pass this argument to a ModelForm instance, as well, and you could probably make it work for custom signals, but that's probably less necessary.

Adding the capability would make working with the build-in signals a lot less of a headache, particularly in my use-case, where a modification to one model with a signal listener attached, triggers a change to another model with a signal listener attached, but I don't want latter listener triggered every time the former is. Let me know if I'm not being clear."		closed	Core (Other)	dev		wontfix	signals	brooks.travis@… michel@…	Design decision needed	1	0	0	0	0	0