-
Notifications
You must be signed in to change notification settings - Fork 118
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 for Django 1.10 and higher? #99
Comments
Using it on two projects with Django 1.10 and 1.11. No issues so far, but my usage is not incredibly advanced. |
Any updates on this ? |
I've issued this on May 8, received response from @jamiecounsell on November 15. It's been a long time and @jamiecounsell claims that it works. I haven't been using Django for a while, so you must trust his words on this. |
@erayerdin so then we need to update documentation about this ) |
@ArtemBernatskyy I definitely think there should be test coverage added for 1.10 and 1.11 before it's added to the documentation. I've been using it just fine, but tox doesn't test 1.10 and 1.11. Maybe check out the repo and just add those versions to the tox.ini and see what breaks. That will at least give you an idea of any risks. I'm still using it, untested, and it's been working fine. I'm not incredibly worried about tests breaking tests, so it's not a huge concern for me, but it should be simple enough to fix up any issues. Maybe I'll look into a PR if I run into any problems. |
My development environment depends on Django 1.10. Builtin tests does not cover anything for 1.10. Is it working on 1.10 or is there any plan to migrate to higher versions of Django?
The text was updated successfully, but these errors were encountered: