Well, it looks like MySQLdb has been inconsistent and not all versions have a "cursors.CursorNW," so it was wrong for me to assume MySQLdb came with that. I've undone the change the introduced that bug.
Adrian On 8/14/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > Sean, > > It appears you're using a version of MySQLdb that doesn't support > CursorNW. I'm using 0.9.2, and it works here. Which version of MySQLdb > are you using? Do this to find out: > > >>> import MySQLdb > >>> MySQLdb.version_info > > Try this in the Python interactive prompt, just to be sure: > > """ > from MySQLdb.cursors import CursorNW > """ > > Adrian > > > > On 8/14/05, Sean O'Donnell <[EMAIL PROTECTED]> wrote: > > > > Hi There, > > > > Im getting an error when trying to follow tutorial 1 when using mysql > > > > when i try to run > > > > django-admin.py init --settings=wasteland.settings.main > > > > > > (Im using tutorial 1 as a template to start a new app called wasteland) > > > > I get > > > > django.core.exceptions.ImproperlyConfigured: Could not load database > > backend: cannot import name CursorNW. Is your DATABASE_ENGINE setting > > (currently, 'mysql') spelled correctly? Available options are: 'mysql', > > 'postgresql', 'sqlite3' > > > > My main.py looks like > > > > DATABASE_ENGINE = 'mysql' # 'postgresql', 'mysql', or 'sqlite3'. > > DATABASE_NAME = 'xxxxx' # Or path to database file if using > > sqlite3. > > DATABASE_USER = 'xxxxx' # Not used with sqlite3. > > DATABASE_PASSWORD = 'xxxxx' # Not used with sqlite3. > > DATABASE_HOST = '' # Set to empty string for localhost. Not > > used with sqlite3. > > > > I ran a svn update, which has had no effect, and I just checked another > > app which i had running with the same config, and realized I cant log > > into its admin site any more, it appears to be having mysql problems as > > well. > > > > Anyone have any ideas? > > > > Thanks > > > > Sean > > > > > > > > > > >
