Make requirements forwards compatible with django. #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make things flexible for apps that use more recent versions of django.
If an application uses a tool such as pip-compile, to seperate top level dependencies and sub dependencies, running pip-compile surfaces the issue that if the version of django used by app using this library and the version required by djangorest-alchemy may be different.
For e.g the following error shows up when running pip-compile for an application that uses django 1.8.4, but since djangoreset-alchemy pins the version to 1.8, pip-compile has issues resolving to the best version.
@ashishgore Might need to make sure djangorest-alchemy actually works with more recent versions of django.