Update requirements
The key thing I wanted to update was the stale pbr req, but I figured I'd just run update-requirements and take what it made :). Change-Id: I65e2556a19d81defb4ee6ceb31a0bec6635efe55
This commit is contained in:
parent
e1079394e3
commit
e185cd0dd3
|
@ -1,7 +1,10 @@
|
||||||
pbr>=0.5.21,<1.0
|
# The order of packages is significant, because pip processes them in the order
|
||||||
Babel>=0.9.6
|
# of appearance. Changing the order has an impact on the overall integration
|
||||||
jinja2
|
# process, which may cause wedges in the gate later.
|
||||||
python-swiftclient>=1.6
|
pbr>=1.6
|
||||||
python-keystoneclient>=0.4.2
|
Babel>=1.3
|
||||||
|
Jinja2>=2.6 # BSD License (3 clause)
|
||||||
|
python-swiftclient>=2.2.0,<=2.3.1
|
||||||
|
python-keystoneclient>=1.6.0
|
||||||
|
PyYAML>=3.1.0
|
||||||
python-magic
|
python-magic
|
||||||
PyYAML
|
|
||||||
|
|
11
setup.py
11
setup.py
|
@ -1,4 +1,3 @@
|
||||||
#!/usr/bin/env python
|
|
||||||
# Copyright (c) 2013 Hewlett-Packard Development Company, L.P.
|
# Copyright (c) 2013 Hewlett-Packard Development Company, L.P.
|
||||||
#
|
#
|
||||||
# Licensed under the Apache License, Version 2.0 (the "License");
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
||||||
|
@ -17,6 +16,14 @@
|
||||||
# THIS FILE IS MANAGED BY THE GLOBAL REQUIREMENTS REPO - DO NOT EDIT
|
# THIS FILE IS MANAGED BY THE GLOBAL REQUIREMENTS REPO - DO NOT EDIT
|
||||||
import setuptools
|
import setuptools
|
||||||
|
|
||||||
|
# In python < 2.7.4, a lazy loading of package `pbr` will break
|
||||||
|
# setuptools if some other modules registered functions in `atexit`.
|
||||||
|
# solution from: http://bugs.python.org/issue15881#msg170215
|
||||||
|
try:
|
||||||
|
import multiprocessing # noqa
|
||||||
|
except ImportError:
|
||||||
|
pass
|
||||||
|
|
||||||
setuptools.setup(
|
setuptools.setup(
|
||||||
setup_requires=['pbr>=0.5.21,<1.0'],
|
setup_requires=['pbr>=1.8'],
|
||||||
pbr=True)
|
pbr=True)
|
||||||
|
|
|
@ -1,12 +1,15 @@
|
||||||
hacking>=0.9.2,<0.10
|
# 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.
|
||||||
|
hacking<0.10,>=0.9.2
|
||||||
|
|
||||||
coverage>=3.6
|
coverage>=3.6
|
||||||
discover
|
discover
|
||||||
fixtures>=0.3.14
|
fixtures>=1.3.1
|
||||||
mock
|
mock>=1.2
|
||||||
python-subunit
|
python-subunit>=0.0.18
|
||||||
sphinx>=1.1.2
|
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
|
||||||
oslosphinx
|
oslosphinx>=2.5.0 # Apache-2.0
|
||||||
testrepository>=0.0.17
|
testrepository>=0.0.18
|
||||||
testscenarios>=0.4,<0.5
|
testscenarios>=0.4
|
||||||
testtools>=0.9.32
|
testtools>=1.4.0
|
||||||
|
|
Loading…
Reference in New Issue