summaryrefslogtreecommitdiffstats
path: root/COPYING.MIT
diff options
context:
space:
mode:
authorMark Asselstine <mark.asselstine@windriver.com>2017-06-20 16:25:54 -0400
committerBruce Ashfield <bruce.ashfield@windriver.com>2017-06-21 14:25:14 -0400
commite86ae39489f1c17405d557f9204747594af29e6a (patch)
tree19896072691430242d237adbb7cf64bdeff5cbd1 /COPYING.MIT
parentb263370eebd1df8befb9533da53c5ff8439607cc (diff)
downloadmeta-virtualization-e86ae39489f1c17405d557f9204747594af29e6a.tar.gz
openvswitch: switch to depending on python3
As far as I can tell openvswitch has been updated to work with python3 as well as with python(2). Switch to depend on python3 and use python3 for associated scripts. For the most part openvswitch will bind at runtime to either py2 or py3 regardless of these changes, with these changes we just do a better job of setting up the dependencies to facilitate py3 bindings. The openvswitch autotests results are mostly identical before and after this switch (failures move from python3 to python(2) test cases as expected, with some exceptions see below). When running the autotests/ptest with python(2) vs python3 we see a slightly higher failure rate (334 failures vs. 284 failures). I do not believe this higher fail rate reflects actual errors in the runtime, rather the tests are not adapted to python3. At any rate like the rest of openvswitch it is fairly straightforward to hack the logic for autotests to be run using py2 as long as it is available in the image, so these changes don't prevent falling back to py2 for autotests. This should facilitate any debugging we need to do based on us switching to favor py3. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'COPYING.MIT')
0 files changed, 0 insertions, 0 deletions