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
25182	Makemigration creates duplicate unlimited migrations when migrating from DateTimeField with auto_add_now to default=timezone.now()	Dmitry Molotkov	nobody	"So if we have a model with a field with auto_add_now=True and then change it to default=timezone.now() django will create a migration with fixed datetime value and will drop a warning that i should use timezone instead of fixed ( well - if timezone should be used why migration not created automatically with it from begin? and if it shouldnt be used in migration - then there shouldnt be this warning).
But thats a minor thing. The major is that even if migration is created it will create a new migraiton with everything same except different hardcoded date on each makemigration. So every run of makemigration will result in new migration added, which is really bad :("	Bug	closed	Migrations	1.8	Normal	invalid			Unreviewed	0	0	0	0	0	0