Django 1.11.* with Python 3.7.* raises a DeprecationWarning

[אורי]

I found out that running tests with deprecation warnings with Django 1.11.18 and Python 3.7.1 raises a DeprecationWarning:

​https://travis-ci.org/speedy-net/speedy-net/jobs/475726532

DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working

I checked on ​https://docs.djangoproject.com/en/dev/releases/1.11/ And Django 1.11 should support Python 3.7, but I don't know about deprecation warnings. Is it OK?

Has this deprecation warning been fixed on Django 2.0 and 2.1?

[Mariusz Felisiak]

This warning has been fixed in ​https://github.com/django/django/commit/aba9763b5117494ca1ef1e420397e3845ad5b262. IMO it is not necessary to backport patch to the Django 1.11, because it won't support Python 3.8.

[אורי]

At least write in the docs that running Django 1.11.* with Python 3.7 with deprecation warnings enabled will raise a DeprecationWarning.

​https://docs.djangoproject.com/en/dev/releases/1.11/

I think you should consider fixing this DeprecationWarning since this version should be supported at least until 2020.

I added a ticket ​https://github.com/django/djangoproject.com/issues/857

[Dylan Young]

NOTE: this doesn't actually affect either Python 3.8 or Python 3.9 compatibility as per the docs:

Deprecated since version 3.3, will be removed in version 3.10: Moved Collections Abstract Base Classes to the collections.abc module. For backwards compatibility, they continue to be visible in this module through Python 3.9.