-
Notifications
You must be signed in to change notification settings - Fork 183
Support Django 2.0 #177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Django 2.0 #177
Conversation
Oops, I wasn't familiar with the Travis CI process. Final 2 commits should have fixed that
Update package version
rfezzani
commented
Mar 16, 2018
I tested it, works fine! Thank you for this contribution. Hope that it will be merged soon.
psyonara
commented
Mar 16, 2018
Thank you, @jasperlittle!
yizhang7210
commented
Mar 16, 2018
Thank you @jasperlittle!!!
psyonara
commented
Mar 23, 2018
Technically, Django 1.8 still has extended support, but this is only until 1 April. And besides we have a much newer LTS in Django 1.11, so dropping 1.8 is a good decision IMO.
deadpyxel
commented
Mar 27, 2018
Is there any prevision for merge?
whitedogg13
commented
Mar 28, 2018
Also watching this. Really hope this great lib can carry on!
niknokseyer
commented
Apr 4, 2018
Hope this get to be a part of a release.
TheBlackDude
commented
Apr 4, 2018
Thanks @jasperlittle
Any ideas when this PR is going to be merged @manosim ???
Hello there! Have given push access to @jasperlittle so he can merge and release 😄
cwirz
commented
Apr 16, 2018
Have tested it and get some regex problems in the template so that the user is not able to test the api there:
screen shot 2018年04月16日 at 20 36 26
screen shot 2018年04月16日 at 20 36 31
deadpyxel
commented
May 7, 2018
Does anyone have the status about this pull request? I see that some regex problems appeared, but is anyone working on a fix?
whitedogg13
commented
May 31, 2018
Hi guys, I just created a new lib supporting Django 1.x and 2.x: django-rest-framework-redocs.
It's also a zero configuration automatic API doc page generator, please take a look and help me make it better!
gracegrimwood
commented
Jun 14, 2018
Is this still a thing?
deadpyxel
commented
Jun 14, 2018
I believe so, but I'm not sure if someone is working on a fix for the reg-ex problem. I am a newbie myself, so I'm not sure if I can really help.
iamhssingh
commented
Jul 16, 2018
Will love to contribute @jasperlittle @manosim
Keep this alive. been using this for a long time!
othreecodes
commented
Jul 18, 2018
merge?
kevincianfarini
commented
Jul 24, 2018
Is there anything else that needs to be done for this to be merged?
liaodalin19903
commented
Jul 24, 2018
@jasperlittle @manosim Hi, friends, can you give the merge access to me? I don't why there still not merge the branch.
ggjersund
commented
Jul 30, 2018
Waiting for this merge as well.
I really need a working, interactive API that supports tokens, as browsable API does not.
novarac23
commented
Jul 31, 2018
+1 on this 😬
live-wire
commented
Aug 31, 2018
Any ETA on merging and releasing this ?
othreecodes
commented
Aug 31, 2018
@jasperlittle @manosim updates?
inoyatov
commented
Nov 14, 2018
How I can use it? Should I install from source?
efazati
commented
Nov 17, 2018
👍
1 similar comment
daspecster
commented
Dec 7, 2018
👍
iamhssingh
commented
Dec 20, 2018
@jasperlittle Can you push and merge? You have the access.
@manosim What about pypi
? Can @jasperlittle also update on pypi
?
@merwok
merwok
Dec 20, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this will cause 1.11.0 to be installed, not any 1.11.*
calina-c
commented
Jul 4, 2019
updates on this?
espoirMur
commented
Nov 4, 2019
@newsuk any update on this?
This pull request aims to provide support for all supported versions of Django and Djano REST Framework.(affecting #175). The support now offered is summarised in the table below:
where 'x' indicates support for python 2.7, 3.4, 3.5 and 3.6.
Support has dropped for Django 1.8 and 1.9, as well as python 3.2 and 3.3. I believe this is for the best, as Django 1.9 and below are considered insecure, and python 3.2 and 3.3 are not supported from Django
1.9 onwards.
Compatibility between Django 1.x and 2.x is achieved by adding a compatibility layer, in a similar manner to that of Django REST Framework
Testing for the various supported configurations is done using tox.