72c501454e
The mock module has been added to Python 3.3 as unittest.mock. The third party mock module doesn't seem to be maintained anymore: the last commit was in April 2013. unittest.mock is more recent, has less bugs and is compatible with Python 3.4. There are bugs on Python 3 in the third party mock module, examples: * https://code.google.com/p/mock/issues/detail?id=225 * https://code.google.com/p/mock/issues/detail?id=234 Oslo Messaging hits these issues when running tests on Python 3.4. Import oslotest to setup six.moves for mock. Change-Id: Ic160101695cea67eb9bbbfcaddb8d3dac64e6804
25 lines
700 B
Plaintext
25 lines
700 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.
|
|
|
|
# Hacking already pins down pep8, pyflakes and flake8
|
|
hacking>=0.10.0,<0.11
|
|
|
|
discover
|
|
fixtures>=0.3.14
|
|
mox3>=0.7.0
|
|
python-subunit>=0.0.18
|
|
testrepository>=0.0.18
|
|
testscenarios>=0.4
|
|
testtools>=0.9.36,!=1.2.0
|
|
oslotest>=1.5.1,<1.6.0 # Apache-2.0
|
|
|
|
# when we can require tox>= 1.4, this can go into tox.ini:
|
|
# [testenv:cover]
|
|
# deps = {[testenv]deps} coverage
|
|
coverage>=3.6
|
|
|
|
# this is required for the docs build jobs
|
|
sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3
|
|
oslosphinx>=2.5.0,<2.6.0 # Apache-2.0
|