#10682: The latest MySQLdb breaks Django
---------------------------------------------------+------------------------
Reporter: twleung | Owner: nobody
Status: closed | Milestone: 1.1
Component: Database layer (models, ORM) | Version: 1.0
Resolution: duplicate | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by kmtracey):
* status: new => closed
* resolution: => duplicate
Comment:
Django hasn't run on "latest trunk" MysqlDB for a long time. There is
some considerable restructuring going on in that code and until it gets
near to a release point it doesn't seem to make a lot of sense to chase
it. #9274 is open to track whatever needs to be done to get Django
running on the next release of MySQLDB.
--
Ticket URL: <http://code.djangoproject.com/ticket/10682#comment:3>
Django <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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
