Now that we're on testtools/testr in places, we can start using
testresources and testscenarios to optimize our test suites a bit.
testresources allows for declarative fixture creation in such a way that
an optimizing test suite can group tests that need an expensive-to-set-up
fixture together and use a reset method on the fixture between tests.
testscenarios allows for declarations of combinations of inputs and outputs
to a single tests, which can greatly simplify large amounts of repetitive
code that's trying to grab coverage of option sets.
Change-Id: I834813071c519086f06f80bf418c949bbc47c0ab
flake8 is the new state-of-the-art for pep8/pyflakes processing. It is
pluggable and configurable and is the basis for the new version of hacking.py.
Change-Id: I7896568836675ae379c14865b5d04c7bcdbd99e2
prior to an aggreed pinning of pep8 in grizzly we ended up with a
rediculous amount of code churn on minor pep8 bumps accross the
projects. It was seen as a huge step forward to pin this to a version
for a release.
We need to not regress this and reintroduce the code churn on pep8
bumps happening upstream, as every single one of them typically
requires a code change on our behalf to integrate. We should take
a single hit at the beginning of a release cycle to the newest pep8
version, and keep it pinned at that till the next release.
Change-Id: I957e98f7e82156a26c86ee5d55c6993486070404
This reverts commit ec00b862b9963ed43242cf2765ccec2cb37f7872
This raises an exception if you try to install it in python2.7, which breaks the mirror script.
(And incidentally means that it must only be conditionally listed as a requirement for python2.6.)
Which is a python2.6-only requirement for kombu. Since we're not yet
building the mirror on python2.6, we need to explicitly list it for
now. Later we will add a mirror builder for each current OpenStack
testing platform.
Change-Id: I5254c5d7fdba8707a6f054ff613cea1619c7c0cc
It is a dependency of keyring that is only listed in setup_requires
and is therefore not detected by the current version of the mirror
script.
Change-Id: I94a7ea266967456ffb2be6c15d95b30cac07bad0
There is a well-known bug in the Paramiko SSH library that causes
these Exceptions:
SSHException: Error connecting via ssh: PID check failed. RNG must be
re-initialized after fork(). Hint: Try Random.atfork()
This bug has been fixed in Paramiko, and therefore we should require
the newer version for Cinder drivers that use Paramiko to function
properly.
Change-Id: I0844db1011f8b5c0e771b0e99a83027a13b6ea75
Fixes: bug 1150720
oslo.config has now been released to PyPI in time for Grizzly RC1 so
we can switch to using it directly.
Change-Id: I655f831718ae5f4e25e941ee206fe195214a9a91
0.7.10 has been released and is compatible with 0.7.x. Instead
of pinning to 0.7.9, simply pin to 0.7.x to avoid SQLAlchemy 0.8
Unfortuantely '<0.8' matches '0.8.0b2', which is what we don't want.
Therefore pinning it to '<=0.7.99' instead.
Change-Id: I14eef50b5a423140421c6e8fe0a5242c2f676fa4
This patch updates tools/pip-requires to use the python-quantumclient 2.2
It also limits the version to <3.0.0 to prevent breaking something accidently
when 3.0.0 is released.
Fixes bug 1152695
Change-Id: I90e5118798ef2fca3b8b07acefe13336479d524f
This is a hacky little script for pulling all of the requirements
from each project into a consolidate pair of pip-requires and
test-requires files.
The output of this can't be passed to 'pip install -r' without
some further sanitation to clean up duplicates.
Change-Id: I47159f744086dc1de1b9fa07ef4cc5a0f85087b0
This is the result of running a script (see next commit) which just
takes all of the pip-requires and test-requires files from our
projects and makes a consolidated list from them.
I had to do some manual cleanup to remove duplicates. This means it's
not a complete list since some of the requires are actually incompatible
like keystoneclient or sqlalchemy.
So, this still isn't sufficient to build a complete PyPI mirror from
yet, but it is closer to the current requirements set and doesn't
artificially pin us to specific versions.
We need to come back around and cap the version ranges according to
each upstream's policy for changing their release numbers when they
make incompatible changes:
http://lists.openstack.org/pipermail/openstack-dev/2013-March/006331.html
Change-Id: I616aa67eee6c559906b2a7a2322686e0c6d846da
