1038f9c8ba
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
14 lines
562 B
Plaintext
14 lines
562 B
Plaintext
# 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
|