summaryrefslogtreecommitdiff
path: root/requirements-test.txt
diff options
context:
space:
mode:
authorStephen Finucane <stephen@that.guru>2019-09-08 17:05:21 +0100
committerStephen Finucane <stephen@that.guru>2019-09-10 15:30:12 +0100
commitc90473ea4478db20a0c7e6686620ad8dd0d412e4 (patch)
tree464298381a0b704bd2aa42783fd13b060659f232 /requirements-test.txt
parent65b76a52e7d018c60fa98244b57e0a52a0f085bf (diff)
downloadpatchwork-c90473ea4478db20a0c7e6686620ad8dd0d412e4.tar
patchwork-c90473ea4478db20a0c7e6686620ad8dd0d412e4.tar.gz
requirements: Switch to compatible releases
In commit ab0c443691, we switched from using commit ranges to fixed ranges. This was a good idea in so far as it ensures we're providing an application with dependencies that are guaranteed to work. However, Patchwork as a project isn't active enough to warrant the continued busy work effort necessary to keep bumping these versions and it's probably about time to abandon the experiment. However, rather than switching back to version ranges, use the compatible releases feature introduced in PEP 440 [1]. This gives us most of the benefits of ranges but with a nicer syntax. [1] https://www.python.org/dev/peps/pep-0440/#compatible-release Signed-off-by: Stephen Finucane <stephen@that.guru>
Diffstat (limited to 'requirements-test.txt')
-rw-r--r--requirements-test.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/requirements-test.txt b/requirements-test.txt
index b1a38c3..6d0b3ef 100644
--- a/requirements-test.txt
+++ b/requirements-test.txt
@@ -1,5 +1,5 @@
-mysqlclient==1.4.4
-psycopg2-binary==2.8.3
-sqlparse==0.3.0
-python-dateutil==2.8.0
-openapi-core==0.8.0
+mysqlclient~=1.4.4
+psycopg2-binary~=2.8
+sqlparse~=0.3
+python-dateutil~=2.8
+openapi-core~=0.8.0