9π
This happened to me when I upgraded various modules using pip
and one of the dependencies automatically upgraded Django to the current version (1.8). You might just check what is your current Django version (pip freeze
) and if itβs 1.8 just downgrade to 1.6 line (pip install -U "Django<1.7"
).
10π
Please note that South is now end of lifed in favour of the βnew migrations framework in Django 1.7, which is based on South but with significant design improvements.
For more details about Django migration framework you can refer release note β https://docs.djangoproject.com/en/1.9/releases/1.7/#schema-migrations
South will not work with Django 1.7; It supports only versions 1.4, 1.5 and 1.6.
- Django error admin.E033: username is not an attribute of users.CustomUser. Why is my custom user admin not working?
- How to load sql fixture in Django for User model?
7π
But the point is how to fix the issue keeping django 1.8 (latest version). I do not think down grading to 1.6 is a good idea because django 1.6 is not a secure version anymore.
- Django Model Field for Abstract Base Class
- Import m2m relation in django-import-export
- Celery workers unable to connect to redis on docker instances
0π
Using django 2.2.4 I realized that βsouthβ was being included in one of my third party installed apps (socket_server). But not on the module, rather, in the migration policies (maybe the guys who created the module are still using an old version of django). So, changed the name from 0001_inicial.py to 0001_inicial_old and django was not able to find it and generated another.
worked as half-measure (socket should install without it)
- Checking if a Django user has a password set
- How to correctly use auto_created attribute in django?
- Django querysets + memcached: best practices