0.10.x release prep, update dependencies (#166)

* Add 0.10.0 changelog

* Fix README formatting on pypi

* Update dependencies

* Simplify travis build matrix

* Use detox for test parallelism

Author: Ryan P Kilby

.travis.yml

@@ -9,16 +9,10 @@ python:
   - "3.5"
   - "3.6"
 
-env:
-  - DJANGO=1.10 REST_FRAMEWORK=3.5
-  - DJANGO=1.9 REST_FRAMEWORK=3.5
-  - DJANGO=1.8 REST_FRAMEWORK=3.5
-  - DJANGO=1.8 REST_FRAMEWORK=3.4
-
 install:
-  - travis_retry pip install tox tox-travis coverage
+  - travis_retry pip install detox tox-travis coverage
 script:
-  - tox -- -v 2
+  - detox -- -v 2
 after_success:
   - coverage report
   - bash <(curl -s https://codecov.io/bash)
@@ -29,11 +23,6 @@ matrix:
       env: TOXENV="performance"
     - python: "3.6"
       env: TOXENV="warnings"
-  exclude:
-    - python: "3.3"
-      env: DJANGO=1.10 REST_FRAMEWORK=3.5
-    - python: "3.3"
-      env: DJANGO=1.9 REST_FRAMEWORK=3.5
   allow_failures:
     - env: TOXENV="warnings"
   fast_finish: true

CHANGELOG.rst

@@ -1,7 +1,26 @@
 Unreleased:
 -----------
 
-* Add support for django-filter 1.0
+v0.10.0:
+--------
+
+This release primarily adds compatibility with django-filter 1.0 (more details
+in #144), and is an intermediate step to overhauling the behavior of filters
+that span relationships.
+
+As `RelatedFilter` is a subclass of `ModelChoiceFilter`, you may take advantage
+of the `callable` behavior for the `queryset` argument. The `queryset` is now a
+required argument, which is a forwards-incompatible change. You can provide the
+model's default queryset to maintain the current behavior, or a callable, which
+will allow you to filter the queryset by the request's properties.
+
+* #124 Removed deprecation warnings
+* #128 Fix all lookups handling for related fields
+* #129 Fix template rendering
+* #139 Fix metaclass inheritance bug
+* #146 Make `RelatedFilter.queryset` a required argument
+* #154 Add python 3.6 support
+* #161 Fix request-based filtering
 
 v0.9.1:
 -------

README.rst

@@ -42,9 +42,9 @@ Features
 Requirements
 ------------
 
-* Python 2.7 or 3.3+
-* Django 1.8, 1.9, 1.10
-* Django REST framework 3.4, 3.5
+* **Python**: 2.7 or 3.3+
+* **Django**: 1.8, 1.9, 1.10, 1.11
+* **DRF**: 3.5, 3.6
 
 
 Installation
@@ -135,7 +135,7 @@ You can easily traverse multiple relationships when filtering by using ``Related
 
 Example filter calls:
 
-.. code-block:: http
+.. code-block::
 
     /api/companies?department__name=Accounting
     /api/companies?department__manager__name__startswith=Bob
@@ -212,7 +212,7 @@ to all filter classes. It incorporates some of the implementation details of the
 
 The above would enable the following filter calls:
 
-.. code-block:: http
+.. code-block::
 
     /api/posts?is_published=true
     /api/authors?posts__is_published=true
@@ -229,23 +229,23 @@ Automatic Filter Negation/Exclusion
 FilterSets support automatic exclusion using a simple ``param!=value`` syntax. This syntax
 internally sets the ``exclude`` property on the filter.
 
-.. code-block:: http
+.. code-block::
 
     /api/page?title!=The%20Park
 
 This syntax supports regular filtering combined with exclusion filtering. For example, the
 following would search for all articles containing "Hello" in the title, while excluding
 those containing "World".
 
-.. code-block:: http
+.. code-block::
 
     /api/articles?title__contains=Hello&title__contains!=World
 
 Note that most filters only accept a single query parameter. In the above, ``title__contains``
 and ``title__contains!`` are interpreted as two separate query parameters. The following would
 probably be invalid, although it depends on the specifics of the individual filter class:
 
-.. code-block:: http
+.. code-block::
 
     /api/articles?title__contains=Hello&title__contains!=World&title_contains!=Friend
 

tox.ini

@@ -1,23 +1,14 @@
 [tox]
 envlist =
     ; Test two versions of DRF against Django's LTS
-    py{27,33,34,35,36}-django18-restframework{34,35},
-    py{27,34,35,36}-django{19,110}-restframework{35},
+    py{27,33,34,35,36}-django18-restframework{35,36},
+    py{27,34,35,36}-django{19,110}-restframework{36},
+    py{27,35,36}-django{111}-restframework{36},
     performance, warnings,
 
 [travis]
 unignore_outcomes = true
 
-[travis:env]
-DJANGO =
-    1.8: django18
-    1.9: django19
-    1.10: django110
-
-REST_FRAMEWORK =
-    3.4: restframework34
-    3.5: restframework35
-
 [testenv]
 commands = coverage run manage.py test {posargs}
 setenv =
@@ -27,8 +18,9 @@ deps =
     django18: django>=1.8.0,<1.9.0
     django19: django>=1.9.0,<1.10.0
     django110: django>=1.10.0,<1.11.0
-    restframework34: djangorestframework>=3.4,<3.5
+    django111: django>=1.11.0,<1.12.0
     restframework35: djangorestframework>=3.5,<3.6
+    restframework36: djangorestframework>=3.6,<3.7
 
 [testenv:performance]
 commands = python manage.py test tests.perf {posargs}