[Django] #30078: Django 1.11.18 with Python 3.7.1 raises a DeprecationWarning

[Django]

#30078: Django 1.11.18 with Python 3.7.1 raises a DeprecationWarning
-------------------------------------+-------------------------------------
Reporter: uri- | Owner: nobody
rodberg |
Type: | Status: new
Uncategorized |
Component: | Version: 1.11
Uncategorized | Keywords: Python 3.7
Severity: Normal | DeprecationWarning
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
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?

--
Ticket URL: <https://code.djangoproject.com/ticket/30078>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#30078: Django 1.11.18 with Python 3.7.1 raises a DeprecationWarning
-------------------------------------+-------------------------------------

Reporter: uri-rodberg | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution: wontfix
Keywords: Python 3.7 | Triage Stage:
DeprecationWarning | Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by felixxm):

* status: new => closed
* resolution: => wontfix

Comment:

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.

--
Ticket URL: <https://code.djangoproject.com/ticket/30078#comment:1>

[Django]

#30078: Django 1.11.18 with Python 3.7.1 raises a DeprecationWarning
-------------------------------------+-------------------------------------

Reporter: uri-rodberg | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution: wontfix
Keywords: Python 3.7 | Triage Stage:
DeprecationWarning | Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by uri-rodberg):

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.

--
Ticket URL: <https://code.djangoproject.com/ticket/30078#comment:2>

[Django]

#30078: Django 1.11.* with Python 3.7.* raises a DeprecationWarning
-------------------------------------+-------------------------------------

Reporter: uri-rodberg | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution: wontfix
Keywords: Python 3.7 | Triage Stage:
DeprecationWarning | Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

--
Ticket URL: <https://code.djangoproject.com/ticket/30078#comment:3>

[Django]

#30078: Django 1.11.* with Python 3.7.* raises a DeprecationWarning
-------------------------------------+-------------------------------------
Reporter: אורי | Owner: nobody

Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution: wontfix
Keywords: Python 3.7 | Triage Stage:
DeprecationWarning | Unreviewed

Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by 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.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/30078#comment:4>