#23446: mysqldb1 is no longer maintained and should not be recommended
-------------------------------------+-------------------------------------
Reporter: frewsxcv | 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: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by timgraham):
Test failures are fixed with mysqlclient 1.3.3. As noted on the thread,
we'll need to drop Python 3.2/MySQL support since the client doesn't
support it. I wonder if mysqlclient has added support for binary data? If
so, we can drop the `supports_binary_field` flag (unless it might be
needed by 3rd party backends). There is also some logic about the minimal
MySQLdb version in `django.db.backends.mysql.base` which will need to be
updated. And of course documentation updates are required.
--
Ticket URL: <https://code.djangoproject.com/ticket/23446#comment:5>
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/066.3ed98a3a50a9c07bc426e212333d8bbc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
