From 115b919cfd2d52f77482be45c7fabeb13341aa20 Mon Sep 17 00:00:00 2001 From: Toshio Kuratomi Date: Mon, 8 Oct 2018 16:43:16 -0700 Subject: [PATCH] [stable-2.6] Mocking out __future__ could cause problems (cherry picked from commit 473f70c) Co-authored-by: Toshio Kuratomi --- .../remote_management/oneview/oneview_module_loader.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/test/units/modules/remote_management/oneview/oneview_module_loader.py b/test/units/modules/remote_management/oneview/oneview_module_loader.py index 9610e10842f..b1c43f484f6 100644 --- a/test/units/modules/remote_management/oneview/oneview_module_loader.py +++ b/test/units/modules/remote_management/oneview/oneview_module_loader.py @@ -4,10 +4,10 @@ import sys from ansible.compat.tests.mock import patch, Mock +# FIXME: These should be done inside of a fixture so that they're only mocked during +# these unittests sys.modules['hpOneView'] = Mock() sys.modules['hpOneView.oneview_client'] = Mock() -sys.modules['future'] = Mock() -sys.modules['__future__'] = Mock() ONEVIEW_MODULE_UTILS_PATH = 'ansible.module_utils.oneview' from ansible.module_utils.oneview import (OneViewModuleException,