#32732: MySQL backend uses deprecated "db" and "passwd" kwargs.
-------------------------------------+-------------------------------------
Reporter: gopackgo90 | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: mysql | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* version: dev => 3.2
* easy: 0 => 1
* keywords: => mysql
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
Thanks for this report.
> Django 2.2, 3.1, and 3.2 all require a minimum version of mysqlclient
newer than 1.3.8, so a fix for this could be backported to all currently
supported versions of Django.
Django 2.2 and 3.1 are in extended support so they don't receive bugfixes
anymore (except security patches). We'll document the maximum supported
version of `mysqlclient` in these versions as soon as deprecated kwargs
are removed.
IMO we can backport this to the Django 3.2 since it's LTS.
--
Ticket URL: <https://code.djangoproject.com/ticket/32732#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.a456bbd38c02f1002c2b782b6adae60a%40djangoproject.com.
