Missing migration for email and is_active changes about django-authtools HOT 4 CLOSED

I believe I fixed this in #67. But there has been no activity here since then, and no new release to pypi.

from django-authtools.

I saw that but wasn't sure as it said Django 1.8 and this doesn't come up unless the project is using 1.9. I can try this again with master if you don't get to it first.

from django-authtools.

Should need the same fix for django 1.9. As far as I can tell, the help_text is the same for 1.8 and 1.9. But it was different for 1.7. So I believe django 1.7 will try to make a new migration. But that would have happened before my fix anyway.

A better solution might be to not hard code the help_text in the migration, but reference whatever django has for it. Not sure what the best thing to do would be. Because now, whenever django changes the help_text, authtools will need a new migration. And each new migration will make previous versions of django try to make a new migration.

from django-authtools.

@jproffitt I can confirm that your patch does fix the initial issue I reported. However now it is detecting new changes without a migration.

Migrations for 'authtools':
  0003_auto_20160128_0851.py:
    - Alter field email on user
    - Alter field is_active on user

Specifically the changes made in these two commits.

• 3080b55
• 8e6b8b9

Updating my issue for this instead.

from django-authtools.