Django 1.7 compatibility

[antonagestam]

fixes #77

Replaced django.http.HttpResponse with django.http.JsonResponse with fallback for Django < 1.7.

[sigvef]

#77 probably affects other parts of the code base as well (e.g. views.py#L301 ), consider moving the JsonResponse shim to a separate file so it can be reused everywhere it is needed.

(I was sent here to review this pull request by http://www.codevolley.com/ , please ignore my comments if they are out of place :) )

[luto]

any news on this? :)

[antonagestam]

@luto I bumped into a lot of problems with migrations in 1.7, so downgraded to 1.6 again. I might spend time on this again once 1.7 is released.

[beaugunderson]

@sigvef The current PR addresses views.py#L301 and I can't find another affected place in the codebase. It also works well for me. 👍 for merging it as 1.7 is now final. :)

I have a fix for test.sh that will be needed for 1.7 as well and will make a PR for that soon but this should get in ASAP.

[beaugunderson]

OK, my PR that fixes tests is ready in #102.

I also ran all of the tests on Django 1.4, 1.5, 1.6, and 1.7 with this pull request applied and they passed cleanly. A merge of #102 and this would be greatly appreciated by those of us using 1.7 now. ✨

[lukmdo]

great, I would add since >= django1.7 comment and maybe move that to provider/compat ?

[egamonal]

Hi, has this been abandoned? looks like this PR is still open

[antonagestam]

@egamonal I think https://github.com/idan/oauthlib is a safer bet these days :)

[egamonal]

thanks @antonagestam , I was trying django-oauth-toolkit to get ready for updating django rest framework to 3.x . I'll give that one a shot as well.