]> git.ipfire.org Git - thirdparty/patchwork.git/commit
requirements: Switch to compatible releases
authorStephen Finucane <stephen@that.guru>
Sun, 8 Sep 2019 16:05:21 +0000 (17:05 +0100)
committerStephen Finucane <stephen@that.guru>
Tue, 10 Sep 2019 14:30:12 +0000 (15:30 +0100)
commitc90473ea4478db20a0c7e6686620ad8dd0d412e4
tree464298381a0b704bd2aa42783fd13b060659f232
parent65b76a52e7d018c60fa98244b57e0a52a0f085bf
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>
requirements-dev.txt
requirements-prod.txt
requirements-test.txt