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
34117	Anomaly with makemigrations	Ismael ABBO	nobody	"== Problem
Makemigrations command does not see the specific change on models related to this field below but produces migrations for any other fields (even in separated project):

{{{
gender = models.BooleanField(
	_('gender'),
	default=True,
	blank=True,
	help_text=_('Designates whether the user is a woman.'),
),
}}}

Adding in migration files works fine, but {{{default}}} value does not (while they're applied in ORM according to [https://docs.djangoproject.com/en/4.1/ref/migration-operations/#addfield])
Then I have added {{{blank=True}}} to counter non-null constraint violation

When I add gender field in the migration files manually, executing {{{makemigrations}}} command again generate a delete of that field {{{gender}}} while I have not removed it in the associate model. **Do we assume here that it does not see the field at all from the beginning? **

When forcefully staying with that field, trying to run a command to populate database produces :
{{{
  File ""/usr/local/lib/python3.9/site-packages/django/db/models/base.py"", line 503, in __init__
    raise TypeError(""%s() got an unexpected keyword argument '%s'"" % (cls.__name__, kwarg))
TypeError: User() got an unexpected keyword argument 'gender'
}}}

**Please, why? Am I wrong somewhere? ** 

== Steps to reproduce with my environment project (but optional because I have tried it in separated project aswell):
- dockerized Postgres 14.4
- dockerized Python 3.8
- Use a CustomUser model by following these instructions (which works well) : [https://code.djangoproject.com/ticket/25313#comment:24]"	Bug	closed	Migrations	3.2	Normal	invalid	CustomUser, field, anomaly	Carsten Fuchs Ed Chai	Unreviewed	0	0	0	0	0	0