From c6e1e6276e1b2c376d0e8c6d50e117df5c631e36 Mon Sep 17 00:00:00 2001 From: Martin Wallgren Date: Thu, 10 Jun 2021 13:12:21 +0200 Subject: [PATCH] Specify open dependencies Declaring fixed version numbers for requirements makes it hard to impossible to use eiffellib in certain circumstances. Libraries should always declare as open dependencies as possible to allow some flexibility for the clients. Should a client not want to allow for this flexibility they can always use a constraints.txt (pip) or poetry.lock (poetry) to lock down the version numbers for any transient dependencies. The other way around is impossible, i.e allow a less restrictive version requirement and the declared requirement from the package. Increasing the jsonschema from an alpha version to the actual release resolves #34. Requiring an alpha release when the actual release was finalized over two years ago is sort of wicked. --- setup.cfg | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/setup.cfg b/setup.cfg index 3e94398..5069fdc 100644 --- a/setup.cfg +++ b/setup.cfg @@ -14,10 +14,10 @@ classifiers = Development Status :: 5 - Production/Stable [options] install_requires = - jsonschema == 3.0.0a2 + jsonschema >= 3.0.0,<4 [options.extras_require] -rabbitmq = pika == 1.0.1 +rabbitmq = pika >= 1.0.1,<2 [files] packages =