From 315aa219434497300e120583bae4d056bacb4c57 Mon Sep 17 00:00:00 2001 From: Matthew Treinish Date: Thu, 13 Oct 2016 17:35:47 -0400 Subject: [PATCH] Fix wording for python3.4 section in the readme The python 3.4 section in the readme was a bit dated since we now also test on python 3.5. This commit attempts to update the wording to explain that it's python >=3.4 not just 3.4. Change-Id: I32ebe4c278b1d5e25cd87ca03f7de1a265334610 --- README.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/README.rst b/README.rst index f1dac1cfb2..fc4de5e61f 100644 --- a/README.rst +++ b/README.rst @@ -196,18 +196,18 @@ 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) -Python 3.4 +Python 3.x ---------- Starting during the Liberty release development cycle work began on enabling Tempest to run under both Python 2.7 and Python 3.4. Tempest strives to fully -support running with Python 3.4. A gating unit test job was added to also run -Tempest's unit tests under Python 3.4. This means that the Tempest code at -least imports under Python 3.4 and things that have unit test coverage will -work on Python 3.4. However, because large parts of Tempest are self-verifying -there might be uncaught issues running on Python 3.4. So until there is a gating -job which does a full Tempest run using Python 3.4 there isn't any guarantee -that running Tempest under Python 3.4 is bug free. +support running with Python 3.4 and newer. A gating unit test job was added to +also run Tempest's unit tests under Python 3. This means that the Tempest +code at least imports under Python 3.4 and things that have unit test coverage +will work on Python 3.4. However, because large parts of Tempest are +self-verifying there might be uncaught issues running on Python 3. So until +there is a gating job which does a full Tempest run using Python 3 there +isn't any guarantee that running Tempest under Python 3 is bug free. Legacy run method -----------------