diskimage-builder/test-requirements.txt

# 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.

pylint==1.7.6;python_version=='2.7' # GPLv2
pylint;python_version>'3.0' #GPLv2

fixtures>=3.0.0 # Apache-2.0/BSD
mock>=2.0.0 # BSD
oslotest>=3.2.0 # Apache-2.0
testrepository>=0.0.18 # Apache-2.0/BSD
testtools>=2.2.0 # MIT

coverage!=4.4,>=4.0 # Apache-2.0

yamllint>=1.23.0
Updated from global requirements Change-Id: Ie2bb534b456ed3aac79b706cf51ecee9789527e4 2014-09-23 01:55:13 +00: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.`
Sync Sphinx requirement 1. Sync sphinx dependency with global requirements. It caps python 2 since sphinx 2.0 no longer supports Python 2.7. 2. Update some URLs to latest 3. Remove the unnecessary space Change-Id: I5464be9e055feecd80918f691448acf5f100e701 2019-06-18 15:25:49 +00:00
Only cap pylint for python2 I noticed that pylint environment doesn't work with Python 3.7; I guess the pinned version has become incompatible. From the history the pin is only for Python 2.7 compatability, so just restrict it to that (with the basepython for the environment set to python3, it's questionable if we still support pylint with 2.7, but anyway). Change-Id: I6a916c8422239a4e1b47dcf28a4569f1637cae7a 2018-11-26 03:48:57 +00:00			`pylint==1.7.6;python_version=='2.7' # GPLv2`
			`pylint;python_version>'3.0' #GPLv2`
Fixed up test-requirements As a first step to OpenStack alignment, get test-requirements.txt in line with current OpenStack standard practices. Fixes: Bug #1205546 Change-Id: I899c3dc167df191b84008250671c58520c436a30 2013-07-27 02:27:45 +00:00
Add missing test requirements, fixup pylint env Add some missing test requirements. I noticed these because pylint was unhappy about the imports if you look closely. Also, pylint shouldn't be in deps as it comes from the parent's "test-requirements.txt" install. We don't need the VIRTUAL_ENV setting either. Change-Id: Ie082a058a9d3d51164448410a00d0719b0b37c4a 2017-06-05 00:25:49 +00:00			`fixtures>=3.0.0 # Apache-2.0/BSD`
Updated from global requirements Change-Id: Ic1d5fe9de580f445e88758e7adc279548ce87e5a 2017-08-24 11:37:04 +00:00			`mock>=2.0.0 # BSD`
Updated from global requirements Change-Id: I3e61c74abb3b4d69ca8d277c964d407c30315493 2018-01-17 20:31:03 +00:00			`oslotest>=3.2.0 # Apache-2.0`
Updated from global requirements Change-Id: I5229ba6b3d21f7902d1af847e0c567a0debedf7a 2016-01-22 04:03:13 +00:00			`testrepository>=0.0.18 # Apache-2.0/BSD`
Updated from global requirements Change-Id: I03dcd2a53ac16425dfa02ce67de4dd959d1bd53d 2017-11-16 11:01:41 +00:00			`testtools>=2.2.0 # MIT`
Create docs site containing element READMEs We currently do not have the ability to create a docs site which outlines all the elements. Change-Id: I77ccf61e0c4b1509b3e7ce9b8f15ea5ccfd50d9b 2015-02-07 10:30:02 +00:00
Updated from global requirements Change-Id: I27d0dbbc14a3d673d9449d0ed8a6f0c52e10257d 2017-05-15 00:42:53 +00:00			`coverage!=4.4,>=4.0 # Apache-2.0`
Revert "dib-lint: use yamllint to parse YAML files" This reverts commit 6ee2995214ee5512c64244ce0ccc7fda639c2d36 and e85c2a6f035a016f80de3d5aebc026f28dfb6bc1. I missed that if you pip install and then run dib-lint, it's not going to pick up the .yamllint file shipped here. Thus it gives spurious errors. The reason for this was simply better duplicate key detection in yaml files, which caused us problems with the kernel installs. However, at this point it seems just the old "does it load" test from pyyaml will be enough. Change-Id: I87a9fc9bb119cfeffad48fc0fa0df31f0181825d 2020-05-28 06:41:01 +00:00
			`yamllint>=1.23.0`