forked from OSchip/llvm-project
[PythonTestSuite] Fix usage of InitializePrivate in PythonTestSuite
llvm-svn: 356950
This commit is contained in:
parent
800fe977d0
commit
e3959de268
|
@ -16,14 +16,19 @@
|
||||||
#include "PythonTestSuite.h"
|
#include "PythonTestSuite.h"
|
||||||
|
|
||||||
using namespace lldb_private;
|
using namespace lldb_private;
|
||||||
|
class TestScriptInterpreterPython : public ScriptInterpreterPython {
|
||||||
|
public:
|
||||||
|
using ScriptInterpreterPython::Initialize;
|
||||||
|
using ScriptInterpreterPython::InitializePrivate;
|
||||||
|
};
|
||||||
|
|
||||||
void PythonTestSuite::SetUp() {
|
void PythonTestSuite::SetUp() {
|
||||||
FileSystem::Initialize();
|
FileSystem::Initialize();
|
||||||
HostInfoBase::Initialize();
|
HostInfoBase::Initialize();
|
||||||
// ScriptInterpreterPython::Initialize() depends on HostInfo being
|
// ScriptInterpreterPython::Initialize() depends on HostInfo being
|
||||||
// initializedso it can compute the python directory etc.
|
// initializedso it can compute the python directory etc.
|
||||||
ScriptInterpreterPython::Initialize();
|
TestScriptInterpreterPython::Initialize();
|
||||||
ScriptInterpreterPython::InitializePrivate();
|
TestScriptInterpreterPython::InitializePrivate();
|
||||||
|
|
||||||
// Although we don't care about concurrency for the purposes of running
|
// Although we don't care about concurrency for the purposes of running
|
||||||
// this test suite, Python requires the GIL to be locked even for
|
// this test suite, Python requires the GIL to be locked even for
|
||||||
|
@ -36,7 +41,7 @@ void PythonTestSuite::SetUp() {
|
||||||
void PythonTestSuite::TearDown() {
|
void PythonTestSuite::TearDown() {
|
||||||
PyGILState_Release(m_gil_state);
|
PyGILState_Release(m_gil_state);
|
||||||
|
|
||||||
ScriptInterpreterPython::Terminate();
|
TestScriptInterpreterPython::Terminate();
|
||||||
HostInfoBase::Terminate();
|
HostInfoBase::Terminate();
|
||||||
FileSystem::Terminate();
|
FileSystem::Terminate();
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue