DeprecationWarning in Django 1.11.22 with Python 3.7

20 views
Skip to first unread message

אורי‎

unread,
Jul 8, 2019, 2:09:16 PM7/8/19
to django...@googlegroups.com
Hi,

I tested Django 1.11.22 (or any version from 1.11.17 to 1.11.22) with Python 3.7, and found out that when running tests with deprecation warnings enabled, I receive the following error:

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

Is this known that Django 1.11 doesn't work with Python 3.7 with deprecation warnings enabled? Does this problem exist with other versions of Django too?

By the way, running tests without deprecation warnings enabled works (the tests pass).

אורי‎

unread,
Jul 8, 2019, 2:28:12 PM7/8/19
to django...@googlegroups.com
I found out that the same DeprecationWarning occurs with Django versions 2.0 and 2.0.13.

Joe Reitman

unread,
Jul 8, 2019, 5:03:58 PM7/8/19
to Django users
Looks like a bug in pyparsing.py

אורי‎

unread,
Jul 9, 2019, 1:12:37 AM7/9/19
to django...@googlegroups.com
I think it's not a bug but a feature of Python which is being deprecated and will be removed in Python 3.8.

I noticed it about 6 months ago and reported in to Django, but it was closed with wontfix.

It has been fixed in https://github.com/django/django/commit/aba9763b5117494ca1ef1e420397e3845ad5b262, but I'm not sure which versions of Django are using this commit.


--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b75d78e1-93a6-43f7-8326-6dc34fbc2ca6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

אורי‎

unread,
Jul 9, 2019, 1:14:36 AM7/9/19
to django...@googlegroups.com
From the branches it looks like all Django versions above 2.1 are using this commit and therefore are fixed.


On Tue, Jul 9, 2019 at 12:04 AM Joe Reitman <jreit...@gmail.com> wrote:
--
Reply all
Reply to author
Forward
0 new messages