#22391: fallback to pymysql if MySQLdb not available
-------------------------------------+-------------------------------------
Reporter: CollinAnderson | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by loic84):
* stage: Unreviewed => Accepted
Comment:
I agree it'd be nice to have support for pymysql, and I actually worked on
it a little while ago before giving up.
I don't think a fallback mechanism is the right approach though, I'd much
prefer a minimal yet separate db backend that'd leverage most of the
implementation of the default backend.
Did you manage to get the test suite to work with this patch? I remember
running into a lot of issues when I tried.
--
Ticket URL: <https://code.djangoproject.com/ticket/22391#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.289e68b13be85383b9319cfd9176ade8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
