#5531: properly report when the mysqldb python package doesn't meet the version
requirements
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner: nobody
Status: reopened | Component: Database wrapper
Version: SVN | Resolution:
Keywords: mysql | Stage: Ready for checkin
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------+--------------------------------------------------
Changes (by ramiro):
* status: closed => reopened
* resolution: invalid =>
Comment:
The OP is reporting that raising {{{ImportError}}} is confusing because it
generates a misleading
"{{{import error no module mysql.base}}}" insted of reporting the unmet
MysQLDb version requeriment.
Here I have a valid environment (ok, actually without a mysql server :)
created by {{{startproject/startapp}}} and I'm algo getting
"{{{ImportError: No module named mysql.base}}}" when simulating the
reported scenario and running {{{manage.py syncdb}}}
Reopening the ticket and posting the proposed fix as a patch (it changes
the error report to "{{{django.core.exceptions.ImproperlyConfigured:
MySQLdb-1.2.1p2 or newer is required; you have x.x.x}}}").
--
Ticket URL: <http://code.djangoproject.com/ticket/5531#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
