openstack
/
tempest
Code Issues Proposed changes

Make tempest's python 2.6 policy clear 

This commit adds a few sentences to the end of the python 2.6 section
in the readme to clearly articulate that there is no python 2.6 in
tempest starting with kilo, and that patches to fix python 2.6 support
will be rejected.

Change-Id: I28b4714e35b84642be47961d3f51343450504db7
This commit is contained in:
Matthew Treinish 2015-02-23 11:52:33 -05:00
parent 643eddee6e
commit d28dd7b7dc
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.rst
View File

@ -124,14 +124,14 @@ run the unit tests with the corresponding version of python.
Python 2.6
----------
Tempest can be run with Python 2.6 however the unit tests and the gate
currently only run with Python 2.7, so there are no guarantees about the state
of tempest when running with Python 2.6. Additionally, to enable testr to work
with tempest using python 2.6 the discover module from the unittest-ext
project has to be patched to switch the unittest.TestSuite to use
unittest2.TestSuite instead. See:
https://code.google.com/p/unittest-ext/issues/detail?id=79
Starting in the kilo release the OpenStack services dropped all support for
python 2.6. This change has been mirrored in tempest, starting after the
tempest-2 tag. This means that proposed changes to tempest which only fix
python 2.6 compatibility will be rejected, and moving forward more features not
present in python 2.6 will be used. If you're running you're OpenStack services
on an earlier release with python 2.6 you can easily run tempest against it
from a remote system running python 2.7. (or deploy a cloud guest in your cloud
that has python 2.7)
Branchless Tempest Considerations
---------------------------------