[BUG] request.DATA usage removed in Django Rest Framework 3.2
See original GitHub issueUsing django-rest-auth 4.0, and upgraded to djangorestframework 3.2 and received the following exception when testing the registration route:
NotImplementedError at /rest-auth/registration/
request.DATA
has been deprecated in favor ofrequest.data
since version 3.0, and has been fully removed as of version 3.2.
request.DATA is appears to be called from rest_framework/request.py line 40.
Issue Analytics
- State:
- Created 8 years ago
- Comments:7
Top Results From Across the Web
3.2 Announcement - Django REST framework
DATA was put on the deprecation path in 3.0. It has now been removed and its usage will result in an error. Use...
Read more >Django Rest Framework: issue with request.data
I get the following error when I attempt to POST. 'WSGIRequest' object has no attribute 'data'. Here is the code for the view.py...
Read more >Middleware - Django documentation
Activating middleware¶ ... To activate a middleware component, add it to the MIDDLEWARE list in your Django settings. ... A Django installation doesn't...
Read more >django-simple-history — django-simple-history 3.2.0.post40+ ...
django-simple-history stores Django model state on every create/update/delete. ... Fixed bug where serializer of djangorestframework crashed if used with ...
Read more >django-axes - PyPI
Fix django.contrib. · Change IP address resolution to allow empty or missing addresses. [aleksihakli] · Add error logging for missing request attributes in...
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
I followed stack trace of error and just replaced request.DATA with request.data in those files which generated errors as per the stack trace. Then It worked fine for me. However I dont know whether it is compatible with django-tests. May be request.DATA have to be replaced with request.data for django-tests.
Ok it does work from master branch, putting git repo link to requirements.txt solved it.