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
18627	Remove django-core uses of Model pre_init and post_init	Jeremy Dunck	Jeremy Dunck	"GenericForeignKey and ImageField use pre_init and post_init - signals which are fired on each model construction.

The signal handling code is heavy relative to plain function dispatch, and is optimized for the zero-handler case.   It's unfortunate that Django ships with these signals being used, as it could instead use an internal hook for the needed initialization, and this approach would be faster.

I'm working on a patch to switch to a more direct hook (which any field could use instead of pre/post_init).

See also: https://groups.google.com/forum/?fromgroups#!search/pre_init$2Fpost_init$20vs.$20performance/django-developers/GNQsvs8X9Gc/cegjyELUZt8J

(Marking triage accepted since discussed and +1'd by some core folks.)"	Cleanup/optimization	closed	Database layer (models, ORM)	1.4	Normal	wontfix			Accepted	1	0	0	0	0	0