-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set default_auto_field to 'AutoField' #223
Comments
This will avoid warnings in Django 3.2 and will avoid the creation of new migrations. closed bennylope#223
For those who are looking for workaround while waiting for the PR #224 to be merged, here's the workaround. GO to your
in your settings.py where you declare your third_party_apps
|
I was very confused by this:
But that if that reads "django-organization's models" then it makes a lot more sense! Thank you @simkimsia! |
Oh right.. sorry! |
@bennylope pls update pypi for a new version if you don't mind. I like to update the dependency so i can stop using the workard i detailed here. |
@simkimsia it's live now, thank you again https://pypi.org/project/django-organizations/#history |
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 django-organization'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.
The specific warning is
Similar in another highly used django library pennersr/django-allauth#2829
EDIT
Change
allauth
todjango-organization
The text was updated successfully, but these errors were encountered: