On Fri, Aug 22, 2008 at 9:34 AM, Russell Keith-Magee <[EMAIL PROTECTED]
> wrote:
> I suspect that re-ordering the imports at the top of mysql.base will
> fix this problem. Open a ticket and I'll put this on my todo list.
>
>
Done, #8485.
Thanks,
Karen
--~--~-~--~~~---
On Fri, Aug 22, 2008 at 9:07 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> Shouldn't the ImproperlyConfigured form the backend's base.py
> get propogated up so that the real cause of the error (MySQLdb either
> missing or too old) can be seen?
This change certainly wasn't intentional. Looking at
I noticed a thread on the user's list (
http://groups.google.com/group/django-users/browse_thread/thread/c0d55dfea1f2a43c#)
reporting that the result of trying to trying to run with the database
backend set to 'mysql' but no MySQLdb installed is now the simple message:
Error: No module named mysql
