diskimage-builder/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.
Babel!=2.4.0,>=2.3.4 # BSD
# NOTE(fdegir): NetworkX 2.3 dropped support for Python 2
networkx>=1.10,<2.3;python_version<'3.0' # BSD
networkx>=1.10;python_version>='3.4' # BSD
pbr!=2.1.0,>=2.0.0 # Apache-2.0
PyYAML>=3.12 # MIT
six>=1.10.0 # MIT
stevedore>=1.20.0 # Apache-2.0
# NOTE(ianw) in here because dib-lint uses flake8
flake8<4.0.0,>=3.6.0 # MIT
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.`
Updated from global requirements Change-Id: I1a8a956293dd7f1973938c60f827705d8b739c3e 2017-04-07 14:22:14 +00:00			`Babel!=2.4.0,>=2.3.4 # BSD`
Constraint networkx to <2.3 for Python 2 NetworkX released 2.3, dropping support for Python 2. https://github.com/networkx/networkx/blob/master/doc/news.rst Depends-On: https://review.openstack.org/#/c/652094 Change-Id: I59afe81d7868605434d2a42658c5b09a6a546732 2019-04-12 12:54:35 +00:00			`# NOTE(fdegir): NetworkX 2.3 dropped support for Python 2`
			`networkx>=1.10,<2.3;python_version<'3.0' # BSD`
			`networkx>=1.10;python_version>='3.4' # BSD`
Updated from global requirements Change-Id: I09b47aa75008bfd832ec8eec9108501f18223875 2017-04-12 04:10:50 +00:00			`pbr!=2.1.0,>=2.0.0 # Apache-2.0`
Updated from global requirements Change-Id: Idf7fa1936a9ee0fc6c3569f8c399f2039cd873a9 2018-03-04 10:01:45 +00:00			`PyYAML>=3.12 # MIT`
Updated from global requirements Change-Id: I03dcd2a53ac16425dfa02ce67de4dd959d1bd53d 2017-11-16 11:01:41 +00:00			`six>=1.10.0 # MIT`
Use stevedore for plugin config of block device This patch introduces stevedore plugin mechanism for use with the block device layer. This makes it possible that other projects pass in their own block device plugins. Change-Id: Id3ea56aaf75f5a20a4e1b6ac2a68adb12c56b574 Signed-off-by: Andreas Florath <andreas@florath.net> 2017-03-17 18:10:04 +00:00			`stevedore>=1.20.0 # Apache-2.0`
Revert "Fixed use of flake8" This reverts commit 74317a34454e3cfbb51ec7e0416b4188f1416418. What I missed was that "dib-lint" is distributed and people use this to lint their out-of-tree elements (e.g. project-config). Because dib-lint runs flake8 that really makes it a valid runtime dependency. However, I don't think we need to pin to these particular versions of flake8 in requirements (which I think was causing the original issues, as it's fairly specific and easily conflicts). It seems to make more sense to use the current uncapped "hacking" versions; so move them from test-requirements.txt. Add a note so we don't forget again. Change-Id: Ic2eee8f5b64c7020e98e0b1ef43a40f24411891a 2019-09-16 00:09:34 +00:00			`# NOTE(ianw) in here because dib-lint uses flake8`
Remove hacking from requirements putting it in requirements means it's installed for anything that installs diskimage-builder. Not just for tests, but in actual prod installations. Because of the way flake8 plugins work, this means then that hacking is injected into all flake8 invocations in that environment. This is currently causing issues in nodepool where we do not actually use hacking but it's still spewing spurious messages to the screen because it is incorrect finding our apache header to be incorrect. Just depend on flake8, since that's what dib-lint depends on. Change-Id: I8d2b2076b604d596906a3b12a5518e2a56c0fe88 2020-03-12 19:42:26 +00:00			`flake8<4.0.0,>=3.6.0 # MIT`