Cortland Klein wrote: > I just had the same problem. It has something to do with MySQLdb not > being included. > >
when it rain's it pours. I'm been hitting my head on the same problem. to verify that this is the case just replace 'mysql' with 'dummy' and you should be able to validate the problem is with the include. regards Ian > For me, I think it's because Mac OS X 10.5.4 doesn't have this python > thing installed. The documentation and tutorial should mention this, > IMO. > > http://code.djangoproject.com/ticket/5531#comment:12 > > On Aug 21, 2008, at 2:52 PM, mpls wrote: > > >> I've edited the DATABASE_ENGINE = 'mysql' in settings.py along with >> specifying a database name and user account info. But I get the >> following error: >> >> ImportError: No module named mysql.base >> >> How can I fix this problem. Any help is appreciated. >> > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
