-
Notifications
You must be signed in to change notification settings - Fork 184
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
base: master
Are you sure you want to change the base?
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
I tested it, works fine! Thank you for this contribution. Hope that it will be merged soon. |
Thank you, @jasperlittle! |
Thank you @jasperlittle!!! |
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. |
Is there any prevision for merge? |
Also watching this. Really hope this great lib can carry on! |
Hope this get to be a part of a release. |
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 😄 |
Does anyone have the status about this pull request? I see that some regex problems appeared, but is anyone working on a fix? |
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! |
Is this still a thing? |
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. |
Will love to contribute @jasperlittle @manosim Keep this alive. been using this for a long time! |
merge? |
Is there anything else that needs to be done for this to be merged? |
@jasperlittle @manosim Hi, friends, can you give the merge access to me? I don't why there still not merge the branch. |
Waiting for this merge as well. |
+1 on this 😬 |
@cwirz I just fixed it. |
Any ETA on merging and releasing this ? |
@jasperlittle @manosim updates? |
How I can use it? Should I install from source? |
👍 |
1 similar comment
👍 |
@jasperlittle Can you push and merge? You have the access. @manosim What about |
Django==1.8.7 | ||
djangorestframework==3.3.2 | ||
coverage==4.0.3 | ||
Django==1.11 |
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.*
updates on this? |
@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.