no South database module 'south.db.sqlite3' , added in apps ,added module in settings ,sill doesnt work ,latest django and south on python 2.7

[Anubhav Kaushik]

 
getting error

There is no South database module 'south.db.sqlite3' for your database. Please either choose a supported database, check for SOUTH_DATABASE_ADAPTER[S] settings, or remove South from INSTALLED_APPS.


latest version of django and south on python 2.7

BELOW IS SETTINGS FILE

"""
Django settings for fuckthisShit project.

Generated by 'django-admin startproject' using Django 1.8.

For more information on this file, see
https://docs.djangoproject.com/en/1.8/topics/settings/

For the full list of settings and their values, see
https://docs.djangoproject.com/en/1.8/ref/settings/
"""

# Build paths inside the project like this: os.path.join(BASE_DIR, ...)
import os

BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))


# Quick-start development settings - unsuitable for production
# See https://docs.djangoproject.com/en/1.8/howto/deployment/checklist/

# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = 'vak_gnh24m!7lkwc99jz0t$h%3x3cyghxg0$)2t57d6)hu!s8_'

# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True

ALLOWED_HOSTS = []


# Application definition

INSTALLED_APPS = (
    'django.contrib.admin',
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.messages',
    'django.contrib.staticfiles',
    'clientmanagement',
    'south',
)

MIDDLEWARE_CLASSES = (
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.auth.middleware.SessionAuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.clickjacking.XFrameOptionsMiddleware',
    'django.middleware.security.SecurityMiddleware',
)

ROOT_URLCONF = 'fuckthisShit.urls'

TEMPLATES = [
    {
        'BACKEND': 'django.template.backends.django.DjangoTemplates',
        'DIRS': [],
        'APP_DIRS': True,
        'OPTIONS': {
            'context_processors': [
                'django.template.context_processors.debug',
                'django.template.context_processors.request',
                'django.contrib.auth.context_processors.auth',
                'django.contrib.messages.context_processors.messages',
            ],
        },
    },
]

WSGI_APPLICATION = 'fuckthisShit.wsgi.application'


# Database
# https://docs.djangoproject.com/en/1.8/ref/settings/#databases

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
    }
}


# Internationalization
# https://docs.djangoproject.com/en/1.8/topics/i18n/

LANGUAGE_CODE = 'en-us'

TIME_ZONE = 'UTC'

USE_I18N = True

USE_L10N = True

USE_TZ = True


# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/1.8/howto/static-files/

STATIC_URL = '/static/'

SOUTH_DATABASE_ADAPTERS = {
    'default': "south.db.sqlite3",
}

[Andrew Godwin]

South only supports Django 1.6 and below - if you're on 1.7 or 1.8, you should be using built-in migrations.

Andrew

--
You received this message because you are subscribed to the Google Groups "South Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to south-users...@googlegroups.com.
To post to this group, send email to south...@googlegroups.com.
Visit this group at http://groups.google.com/group/south-users.
For more options, visit https://groups.google.com/d/optout.

[bijan....@sirono.com]

Anubhav:

The 'generic.py' module merely needs to be patched to get this to behave with Django 1.8 (see attached)

Andrew:

Although people update their own application code to use Django migrations, they often use many Django add-on libraries which are still using South (e.g. admin_tools, djcelery, gargoyle, kombu, rest_framework, social_auth, just to name a few).   

Would it be possible to make another minor fix release with the attached patch so that people aren't left in a 'migrate' limbo?  I understand that South is being end-of-lifed but I think the issue mentioned by Anubev is going to be treated unnecessarily as a roadblock for many people to move safely and naturally to Django 1.8 (and its new migrations).

Cheers,

[Andrew Godwin]

I'm afraid there's going to be no more releases - I'm not willing to support South on Django 1.7 and up, for reasons I've stated before. If you want to maintain a fork you're more than welcome, but there are more subtle issues than can be fixed with just a simple patch to the database backend (such as command overriding).

Andrew

--

[Maurin Johan]

Hello i had the same problem.  You have two choice. Put 'south' in INSTALLED_APPS or

SOUTH_DATABASE_ADAPTERS = {
'default': 'south.db.sqlite3'}

And when you put them at the same time you have this error.

If that don't work may be your answer can be here :http://answerhub.com/qa/questions/28185/how-do-i-get-syncdb-to-work-im-getting-there-is-no.html

[Maurin Johan]

Sorry about my last post he is wrong. 

In fact the problem come from your django version. You need the 1.6 version.

http://stackoverflow.com/questions/29478400/there-is-no-south-database-module-south-db-postgresql-psycopg2-for-your-databa