Update support for Python, Django and DRF libs #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
December 11, 2017 14:24
Drop support for Python 3.3 Drop support for Django 1.6, 1.7, 1.9, 1.10 (See 'Supported Versions' on https://www.djangoproject.com/download/) Drop support for DRF 2 (DRF 2 does not support Django 1.8 or newer) Add support for DRF 3.2, 3.3, 3.4, 3.5, 3.6, 3.7 Add support for Django 1.11, 2.0 Add support for Python 3.6, 3.7
|
Supersede by #32 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the envs that get tested with current versions. I hope Travis agrees, as I'm unable to test everything locally :). It might be wise to start culling the list of DRF versions that you want to support, but I couldn't find an overview of which versions DRF itself still supports.