Set default_auto_field to 'AutoField'

[Flimm]

Django 3.2 introduces DEFAULT_AUTO_FIELD . If you set this to something other than 'django.db.models.AutoField', migrations will need to be generated for allauth's models. This pull request sets default_auto_field just for these apps so that no migrations need to be generated.

It also hides warnings on Django 3.2.

Fixes: #2826

[coveralls]

Coverage increased (+0.001%) to 93.581% when pulling 3c1f7fe on Flimm:avoid_auto_field_warnings into 3533862 on pennersr:master.

[czue]

What's the status of this issue? Any plans for a merge/release anytime soon?

[adamchainz]

It would be better to migrate all the models to BigAutoField with explicit declarations. This would prevent them from exhausting ID's, which is the reason Django added DEFAULT_AUTO_FIELD in the first place. But that might be a major version bump.

[czue]

Yeah agreed that makes sense in the long term. In the short term the creation of these migrations can be problematic for new projects, which can easily introduce migrations that depend on files that only exist in a virtualenv on a single dev's machine, and then lead to confusing "missing migration" error when trying to deploy on another environment.

If the release process isn't too painful, do you think it might make sense to roll the fixes out in two stages to avoid people getting tripped up in the interim?

[adamchainz]

Two fixes would be a good idea, yes. (I am not a maintainer, just a user.)

[simkimsia]

While waiting for this to be merged, what's a regular user to do to at least temporary suppress the warning without triggering a migration file at least?

[Flimm]

While waiting for this to be merged, what's a regular user to do to at least temporary suppress the warning without triggering a migration file at least?

My post on Stack Overflow explains a workaround. Also, be aware of this bug #2853.

[simkimsia]

@Flimm

Thank you. HOwever, when I followed your workaround including the one for bug #2853, i get the following

ERRORS:
django_1    | account.EmailAddress.user: (fields.E301) Field defines a relation with the model 'auth.User', which has been swapped out.
django_1    | 	HINT: Update the relation to point at 'settings.AUTH_USER_MODEL'.
django_1    | socialaccount.SocialAccount.user: (fields.E301) Field defines a relation with the model 'auth.User', which has been swapped out.
django_1    | 	HINT: Update the relation to point at 'settings.AUTH_USER_MODEL'

Suggestions?

Update

Forget it. I just realized is similar to the issue raised by @Flimm

So I wrote the workaround in #2946

[brianhelba]

@pennersr This is an important compatibility fix for Django 3.2, and it's generated significant user attention. Could you please review this?

After this is merged, could we also get a PyPI release?

[Flimm]

Yay! Thank you for merging.

[brianhelba]

@pennersr Thanks! Could you issue a new PyPI release to include this change?

[Reston]

I had this problem!

Waiting for this to be released 😄

@pennersr any update?

[Flimm]

The latest release on PyPI does contain the fix, now.