swift

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.

Remove dependencies on pep8, pyflakes and flake8 They should be determined by the hacking dependency implicitely. Change-Id: I8805f7b0ef9f2b1f59be342e9c6d032330707688

2014年01月16日 13:39:08 +01:00

# Hacking already pins down pep8, pyflakes and flake8

lint: Up-rev hacking Last time we did this was nearly 4 years ago; drag ourselves into something approaching the present. Address a few new pyflakes issues that seem reasonable to enforce: E275 missing whitespace after keyword E231 missing whitespace after ',' E721 do not compare types, for exact checks use `is` / `is not`, for instance checks use `isinstance()` Main motivator is that the old hacking kept us on an old version of flake8 et al., which no longer work with newer Pythons. Change-Id: I54b46349fabb9776dcadc6def1cfb961c123aaa0

2024年02月07日 22:27:13 +00:00

hacking>=2.0,<6.2.0 # Apache-2.0

Switch to pytest nose has not seen active development for many years now. With py310, we can no longer use it due to import errors. Also update lower contraints Closes-Bug: #1993531 Change-Id: I215ba0d4654c9c637c3b97953d8659ac80892db8

2022年07月26日 15:07:35 -07:00

coverage>=5.0.4 # Apache-2.0

pytest>=4.6.11 # MIT

pytest-cov>=2.12.1 # MIT

Give functional tests another chance to pass In the process, move from using os-testr to stestr. Change-Id: Ib6651aab8b009605bf0855ec217003936c0fae6e

2021年03月25日 13:06:24 -07:00

stestr>=2.0.0 # Apache-2.0

lower-constraints: update to mock 3.0 The main motivation here is that mock.call becomes a namedtuple and you can say `m.call_args_list[0].args` instead of `m.call_args_list[0][0]` Change-Id: Ibb1a64ef0bfdebf06d26636cdb6ea191c10705f7

2024年04月04日 10:36:36 -05:00

mock>=3.0 # BSD

Set lower bounds on all requirements and test-requirements I just took these from the current versions at https://github.com/openstack/requirements/blob/master/lower-constraints.txt so we can get the the change we *actually* want, which is to black-list a known-bad version of eventlet. Change-Id: I9842c9975821bda5c7d8bf2fc214480c0c0a5e96

2018年06月15日 10:42:08 -07:00

python-swiftclient>=3.2.0

Update test-requirements.txt The testing requirements should not cause extra packaging work for deployers (since these aren't required to deploy). This patch brings it in line with the latest global requirements, except for python-swiftclient itself (which I kept with no version specifier). By being in line with global requirements, this is a more accurate list with respect to how things are actually tested in the gate. Change-Id: Iddc92d9bb135144d38c3e5aec2e95df5787e9b5b

2016年09月03日 10:18:32 -07:00

python-keystoneclient!=2.1.0,>=2.0.0 # Apache-2.0

Set lower bounds on all requirements and test-requirements I just took these from the current versions at https://github.com/openstack/requirements/blob/master/lower-constraints.txt so we can get the the change we *actually* want, which is to black-list a known-bad version of eventlet. Change-Id: I9842c9975821bda5c7d8bf2fc214480c0c0a5e96

2018年06月15日 10:42:08 -07:00

boto>=2.32.1

Start transition to boto3 in s3api tests. Adds the scaffolding required for tests to use boto3 and converts the test_bucket.py tests to the new interface. Follow on patches will convert the other tests to use the boto3 library. Notable changes: we no longer try to reach for the equivalent of `boto.make_request()` and instead rely on the boto3/botocore event system to mutate requests as necessary (or to disable pre-flight validators). Partial-Bug: 1557260 Change-Id: I3d77ef4a6b878c49ebfa0c8b8647d7199d87601e

2019年05月04日 12:11:54 -07:00

boto3>=1.9

botocore>=1.12

Import swift3 into swift repo as s3api middleware This attempts to import openstack/swift3 package into swift upstream repository, namespace. This is almost simple porting except following items. 1. Rename swift3 namespace to swift.common.middleware.s3api 1.1 Rename also some conflicted class names (e.g. Request/Response) 2. Port unittests to test/unit/s3api dir to be able to run on the gate. 3. Port functests to test/functional/s3api and setup in-process testing 4. Port docs to doc dir, then address the namespace change. 5. Use get_logger() instead of global logger instance 6. Avoid global conf instance Ex. fix various minor issue on those steps (e.g. packages, dependencies, deprecated things) The details and patch references in the work on feature/s3api are listed at https://trello.com/b/ZloaZ23t/s3api (completed board) Note that, because this is just a porting, no new feature is developed since the last swift3 release, and in the future work, Swift upstream may continue to work on remaining items for further improvements and the best compatibility of Amazon S3. Please read the new docs for your deployment and keep track to know what would be changed in the future releases. Change-Id: Ib803ea89cfee9a53c429606149159dd136c036fd Co-Authored-By: Thiago da Silva <thiago@redhat.com> Co-Authored-By: Tim Burke <tim.burke@gmail.com>

2017年10月16日 21:39:12 +09:00

requests-mock>=1.2.0 # Apache-2.0

keystonemiddleware>=4.17.0 # Apache-2.0

Adding bandit for security static analysis testing in swift This change adds a basic bandit config for Swift. It can be invoked by running the tox environment for bandit; tox -e bandit This is an initial step for using bandit with Swift and it should be revisited to improve the testing as more is learned about the specific needs of the Swift code base.As per now some tests are excluded as they were used on purpose. https://wiki.openstack.org/wiki/Security/Projects/Bandit Implements: blueprint swift-bandit Change-Id: I621be9a68ae9311f3a6eadd1636b05e646260cf2

2015年06月27日 23:26:47 +05:30

# Security checks

Update test-requirements.txt The testing requirements should not cause extra packaging work for deployers (since these aren't required to deploy). This patch brings it in line with the latest global requirements, except for python-swiftclient itself (which I kept with no version specifier). By being in line with global requirements, this is a more accurate list with respect to how things are actually tested in the gate. Change-Id: Iddc92d9bb135144d38c3e5aec2e95df5787e9b5b

2016年09月03日 10:18:32 -07:00

bandit>=1.1.0 # Apache-2.0

Added PyPI validation check for the readme. See https://review.openstack.org/#/c/571007/ and https://review.openstack.org/#/c/570999/ for context. Change-Id: Ib6045de3cb9097ed7e6d48646109f35612cbbc74

2018年05月30日 07:40:38 -07:00

Set lower bounds on all requirements and test-requirements I just took these from the current versions at https://github.com/openstack/requirements/blob/master/lower-constraints.txt so we can get the the change we *actually* want, which is to black-list a known-bad version of eventlet. Change-Id: I9842c9975821bda5c7d8bf2fc214480c0c0a5e96

2018年06月15日 10:42:08 -07:00

docutils>=0.11 # OSI-Approved Open Source, Public Domain

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

24 lines

712 B

Plaintext

Raw Normal View History

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

24 lines 712 B Plaintext Raw Normal View History Unescape Escape

24 lines

712 B

Plaintext

Raw Normal View History