MySQL 5.5 is end-of-life in December 2018. Usually we drop support for a particular database version in the Django release prior to the end-of-life date [0], so that would mean dropping support in Django 2.1 (released August 2018). We don't have MySQL 5.5 testing in our continuous integration servers and in local testing, I noticed some GIS test failures with MySQL 5.5. Before investigating them, I thought I'd ask to see if there might be consensus to drop support for MySQL 5.5 in Django 2.0 instead of 2.1. I'd guess anyone using MySQL 5.5 users would stick with Django 1.11 LTS or older.
https://github.com/django/django/pull/8980 shows the cleanups for removal of MySQL 5.5 support. Also, MySQL 5.5 is the last usage among the built-in database backends for the supports_microsecond_precision database feature so there's a chance that could be removed also, though I found usage of it in django_pyodbc [1]. [0] https://code.djangoproject.com/wiki/SupportedDatabaseVersions -- though we've made some exceptions like dropping support earlier for Oracle 11, https://groups.google.com/forum/#!topic/django-developers/IawbBWzPXaA/discussion [1] https://github.com/lionheart/django-pyodbc/issues/87 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/367b0ca0-1ec9-48b6-a513-4c66a30c491d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
