@@ -8,14 +8,14 @@ ignore_basepython_conflict = true
basepython = python3
deps =
-r{toxinidir}/requirements-test.txt
- django22: django>=2.2,<2.3
- django22: djangorestframework>=3.10,<3.13
+ django22: django~=2.2.0
+ django22: djangorestframework~=3.12.0
django22: django-filter~=21.1.0
- django31: django>=3.1,<3.2
- django31: djangorestframework>=3.10,<3.13
+ django31: django~=3.1.0
+ django31: djangorestframework~=3.12.0
django31: django-filter~=21.1.0
- django32: django>=3.2,<3.3
- django32: djangorestframework>=3.10,<3.13
+ django32: django>=3.2.0
+ django32: djangorestframework~=3.12.0
django32: django-filter~=21.1.0
setenv =
DJANGO_SETTINGS_MODULE = patchwork.settings.dev
As we previously did for the requirements files (commit c90473ea44), switch to use compatible releases for tox. We previously avoided doing this on the basis that the existing system gave an idea of supported package versions, but we weren't actually testing these combinations since pip will always install the latest available version of each package. This will apply to anyone using pip to manage their dependencies, while anyone using distro packages can rely on the distro having done this testing for them. Given the above, this makes our effort to track supported ranges moot. So long as we cap newer versions of e.g. django-filter when they're not compatible with older Django versions, we should be good. Signed-off-by: Stephen Finucane <stephen@that.guru> --- tox.ini | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)