openstack/swift - swift - OpenDev: Free Software Needs Free Tools

This website requires JavaScript.

openstack/swift

Code Issues Proposed changes

Files

768104b8ecace8affcc0880d2a529df30d82ee75

swift /requirements.txt

14 lines

482 B

Plaintext

Raw Normal View History

warn against sorting requirements Change-Id: I64ae9191863564e278a35d42ec9cd743a233028e Closes-Bug: 1365061

2014年09月03日 12:03:40 -05:00

# The order of packages is significant, because pip processes them in the order

# of appearance. Changing the order has an impact on the overall integration

# process, which may cause wedges in the gate later.

Update dnspython to 1.14 dnspython 1.14 adds Python 3 support and so can now be used on Python 2 and Python 3. Drop dnspython3 dependency. Change-Id: I0a860b03800aeeed4375f528e6bf9cca57129db7

2016年06月29日 09:30:34 +02:00

dnspython>=1.14.0 # http://www.dnspython.org/LICENSE

Bump eventlet min version to 0.17.4 IPv6 support in Swift is dependent on IPv6 support in eventlet. eventlet itself only claims support for IPv6 post v0.17 (https://github.com/eventlet/eventlet/issues/8). This update matches the OpenStack global requirements version. Change-Id: I9d8433cdd3bf7d7a93b8f50b991cc21721a80d22

2016年01月19日 10:30:30 -08:00

eventlet>=0.17.4 # MIT

Use install_requires in setup.py Using install_requires makes sure that if some code is using Swift internal and wants to require Swift, all its dependencies have been already pulled. This is really useful on test automation for example, otherwise, code might be failing because on of the module listed in pip-requires is not instaled. Also, we change the pip-requires files to use >= rather than ==, so the requirements are easily fulfiled with distribution provided packages. Change-Id: I65814bcd8ce798da21a5c17b4d5916a23f59e962 Signed-off-by: Julien Danjou <julien@danjou.info>

2012年12月04日 12:38:26 +01:00

greenlet>=0.3.1

taking the global reqs that we can Change-Id: Icfdeeab14e90728aa8167ad6587d51e9b10cb846

2014年05月21日 09:37:22 -07:00

netifaces>=0.5,!=0.10.0,!=0.10.1

Use install_requires in setup.py Using install_requires makes sure that if some code is using Swift internal and wants to require Swift, all its dependencies have been already pulled. This is really useful on test automation for example, otherwise, code might be failing because on of the module listed in pip-requires is not instaled. Also, we change the pip-requires files to use >= rather than ==, so the requirements are easily fulfiled with distribution provided packages. Change-Id: I65814bcd8ce798da21a5c17b4d5916a23f59e962 Signed-off-by: Julien Danjou <julien@danjou.info>

2012年12月04日 12:38:26 +01:00

pastedeploy>=1.3.3

Add six requirement The six module is needed to add Python 3 support to Swift. Change-Id: Ie637ed3458c7ff56c26834bca73203ed55604d74

2015年06月09日 00:22:12 +02:00

six>=1.9.0

Use install_requires in setup.py Using install_requires makes sure that if some code is using Swift internal and wants to require Swift, all its dependencies have been already pulled. This is really useful on test automation for example, otherwise, code might be failing because on of the module listed in pip-requires is not instaled. Also, we change the pip-requires files to use >= rather than ==, so the requirements are easily fulfiled with distribution provided packages. Change-Id: I65814bcd8ce798da21a5c17b4d5916a23f59e962 Signed-off-by: Julien Danjou <julien@danjou.info>

2012年12月04日 12:38:26 +01:00

xattr>=0.4

Bump PyECLib requirement to >= 1.2.0 This was discussed at last Swift meeting [1] and conclusion was to require newest PyECLib version. [1] http://eavesdrop.openstack.org/meetings/swift/2016/swift.2016年02月10日-21.00.log.html#l-268 Depends-On: I0fd58f26bc0a3e7715356ff74344981f22786152 Change-Id: I54e89d99b48e00e614d2d457814c00354763c83b

2016年02月11日 10:20:10 +01:00

PyECLib>=1.2.0 # BSD

Enable object body and metadata encryption Adds encryption middlewares. All object servers and proxy servers should be upgraded before introducing encryption middleware. Encryption middleware should be first introduced with the encryption middleware disable_encryption option set to True. Once all proxies have encryption middleware installed this option may be set to False (the default). Increases constraints.py:MAX_HEADER_COUNT by 4 to allow for headers generated by encryption-related middleware. Co-Authored-By: Tim Burke <tim.burke@gmail.com> Co-Authored-By: Christian Cachin <cca@zurich.ibm.com> Co-Authored-By: Mahati Chamarthy <mahati.chamarthy@gmail.com> Co-Authored-By: Peter Chng <pchng@ca.ibm.com> Co-Authored-By: Alistair Coles <alistair.coles@hpe.com> Co-Authored-By: Jonathan Hinson <jlhinson@us.ibm.com> Co-Authored-By: Hamdi Roumani <roumani@ca.ibm.com> UpgradeImpact Change-Id: Ie6db22697ceb1021baaa6bddcf8e41ae3acb5376

2016年06月07日 15:01:32 +01:00

cryptography>=1.0,!=1.3.0 # BSD/Apache-2.0

Copy Permalink