Since DRF 3.2 now supports Django 1.8 can we update this to as well?

Question

Since DRF 3.2 now supports Django 1.8 can we update this to as well?

alan-unravel opened this issue 9 years ago · 5 comments

As above

Answer 1 · 2015-09-08T15:59:22.000Z

do you mean all the deprecated things like request.data vs request.DATA, etc?

Answer 2 · 2015-09-09T07:59:46.000Z

It was more of a question, the README states that this doesn't support >Django1.7 since DRF 3 does not but DRF 3.2(which I believe to be the current version) does. Do you foresee anything breaking if I try to use this 1.8 and DRF 3.2?

Answer 3 · 2015-09-10T03:18:08.000Z

Sorry for late response. At the conference now. When I get back Ill verify that it works with 3.2 but as far as I know it should still continue working with 3.2. If not Ill fix that and will add a patch.

Answer 4 · 2015-09-10T08:30:38.000Z

That would be great, thanks. I have it up and seemingly running on 3.2 so it shouldn't take much work if any! Thanks again.

Answer 5 · 2016-05-18T19:51:25.000Z

I think this could be better clarified in the README to explain DRF < 3.0 requires Django < 1.8, but DRF > 3.0 has no specific Django requirement (it follows the DRF requirements).