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
Remove unused import patterns, fix project for Django > 1.8 #13
Conversation
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.
Thanks for the pull request! This project definitely needs to be updated. If I support Django 1.10 and 1.11, those versions need to added to the tox tests. Are you familiar with tox?
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.
Could edit this pull request so it will be merged into develop?
|
||
[testenv] | ||
deps = | ||
pytest | ||
pytest-django | ||
django18: Django==1.8.10 | ||
django19: Django==1.9.3 | ||
django110: Django==1.10.4 |
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.
Please add the latest Django version also: 1.11.1 I believe.
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 havent personally tried it with Django=1.11.1. Let me get travis run it on 1.10.4, and if that goes green - will add for sure.
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 have a branch that takes care of most it if you want to add 1.11.1 and change the base to develop we can merge it.
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 am trying to fix the issues with 1.10 now. Looks like some reverse
imports from somewhere else post 1.10.
Ah. missed that :-( |
Alright. Let me push this to the development branch. |
If the tests pass, I think we are done here. |
Thanks! |
The import was showing up error on later Django versions (Now its 1.11+)