[Fixed]-There is no South database module 'south.db.postgresql_psycopg2' for your database

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").

πŸ‘€kravietz

70πŸ‘

Try pip uninstall South, then you will see if your application is 1.8 ready.

πŸ‘€Papa Sax

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.

πŸ‘€WangST

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.

πŸ‘€Lahiru

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)

πŸ‘€Rafael

Leave a comment