From e3959de26867d65410d4d5e1fc8c9c8f5bb2951a Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere <jonas@devlieghere.com>
Date: Mon, 25 Mar 2019 21:07:53 +0000
Subject: [PythonTestSuite] Fix usage of InitializePrivate in PythonTestSuite

llvm-svn: 356950
---
 lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

(limited to 'lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp')

diff --git a/lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp b/lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp
index 8c4e28114bc..26b8bafdd8d 100644
--- a/lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp
+++ b/lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp
@@ -16,14 +16,19 @@
 #include "PythonTestSuite.h"
 
 using namespace lldb_private;
+class TestScriptInterpreterPython : public ScriptInterpreterPython {
+public:
+  using ScriptInterpreterPython::Initialize;
+  using ScriptInterpreterPython::InitializePrivate;
+};
 
 void PythonTestSuite::SetUp() {
   FileSystem::Initialize();
   HostInfoBase::Initialize();
   // ScriptInterpreterPython::Initialize() depends on HostInfo being
   // initializedso it can compute the python directory etc.
-  ScriptInterpreterPython::Initialize();
-  ScriptInterpreterPython::InitializePrivate();
+  TestScriptInterpreterPython::Initialize();
+  TestScriptInterpreterPython::InitializePrivate();
 
   // Although we don't care about concurrency for the purposes of running
   // this test suite, Python requires the GIL to be locked even for
@@ -36,7 +41,7 @@ void PythonTestSuite::SetUp() {
 void PythonTestSuite::TearDown() {
   PyGILState_Release(m_gil_state);
 
-  ScriptInterpreterPython::Terminate();
+  TestScriptInterpreterPython::Terminate();
   HostInfoBase::Terminate();
   FileSystem::Terminate();
 }
-- 
cgit v1.2.3