Currently incompatible with Django 4.0: uses providing_args argument
See original GitHub issueI’ve installed the newly released Django 4.0. I get an error when running this code:
from notifications.signals import notify
The error is:
File "example/.venv/lib/python3.9/site-packages/notifications/signals.py", line 5, in <module>
notify = Signal(providing_args=[ # pylint: disable=invalid-name
TypeError: __init__() got an unexpected keyword argument 'providing_args'
As you can see in the release notes for Django 4.0, this version no longer supports the providing_args
named argument for Signal
.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
python - TypeError: __init__() got an unexpected keyword ...
I ran into a similar issue. However, I was not using AllAuth . The problem is that Django 4.0 does not have any...
Read more >Django 4.0 release notes
Django test runner now supports a --buffer option with parallel tests. The new logger argument to DiscoverRunner allows a Python logger to be ......
Read more >Change Log - django-auth-ldap - Read the Docs
Honor the attrlist argument to AUTH_LDAP_GROUP_SEARCH · Backwards incompatible: Removed support for Django < 1.11. · Support for Python 2.7 and 3.4+ now...
Read more >django Changelog - pyup.io
want to be aware of when upgrading from Django 4.0 or earlier. We've ... The ``providing_args`` argument for ``django.dispatch.Signal`` is removed.
Read more >Release Notes - Django REST framework
You can determine your currently installed version using pip show : pip show djangorestframework ... (Due to incompatibility with DjangoRedis cache backend.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The fix is as easy as modifying
notifications/signals.py
to change this line from:to:
@max-wittig I can review, but I have no rights to merge. @nemesisdesign Did merge my MR a year ago.