Bug #98346 Compatibility issue with Django 3.x
Submitted: 24 Jan 2020 11:40 Modified: 10 Aug 2022 20:58
Reporter: Nicolas Bérigaud Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / Python Severity:S4 (Feature request)
Version:8.0.19 OS:Any
Assigned to: CPU Architecture:Any

[24 Jan 2020 11:40] Nicolas Bérigaud
Description:
Hi,

Django in the the release 3.x remove support for Python 2, some APIs bundled get removed, including six.
https://docs.djangoproject.com/en/3.0/releases/3.0/#removed-private-python-2-compatibility...

The mysql-connector-python try to import six from django.utils
https://github.com/mysql/mysql-connector-python/blob/master/lib/mysql/connector/django/bas...

How to repeat:
Start any django 3.x project with mysql.connector.django as DB ENGINE.

Suggested fix:
Use global six
[24 Jan 2020 11:41] Nicolas Bérigaud
Traceback

Attachment: traceback.txt (text/plain), 3.42 KiB.

[31 Jan 2020 6:59] MySQL Verification Team
Hello Nicolas,

Thank you for the report and feedback.

regards,
Umesh
[10 Aug 2022 20:58] Philip Olson
Posted by developer:
 
Sorry for the delay, this was fixed in v8.0.22 via another bug and here's the release note:

  Added Django 3.0 support while preserving compatibility with
  Django 2.2. Removed support for Django 1.11 with Python 2.7.