Repository navigation
PInvokeStackImbalance #485
Description
Environment
- Pythonnet version: pythonnet_py35_dotnet v2.3.0 (from NuGet)
- Python version: Python 3.5.3
- Operating System: Windows 7 x86_64
Details
- When I try to intialise the interpreter, I get this message:
Managed Debugging Assistant 'PInvokeStackImbalance' : 'A call to PInvoke function 'Python.Runtime!Python.Runtime.Runtime::Py_SetPythonHome' has unbalanced the stack. This is likely because the managed PInvoke signature does not match the unmanaged target signature. Check that the calling convention and parameters of the PInvoke signature match the target unmanaged signature.'
The code I'm using is
PythonEngine.PythonHome = pypath;
PythonEngine.ProgramName = "PythonAPI";
PythonEngine.Initialize();
pylock = PythonEngine.AcquireLock();
AppDomain.CurrentDomain.ProcessExit += (o, a) => { PythonEngine.ReleaseLock(pylock); };
PythonEngine.Exec(Properties.Resources.PythonAPI);
and the exception occurs on the first line. pypath points to a directory containing the entire contents of the "Windows x86 embeddable zip file" of Python 3.5.3 on python.org.
Activity
den-run-ai commentedon Jun 10, 2017
DeclanHoare commentedon Jun 11, 2017
Having installed that I can use the clr module from within Python to interact with C# types perfectly, but I can't see how to embed that in my .NET application.
den-run-ai commentedon Jun 11, 2017
DeclanHoare commentedon Jun 11, 2017
With this method, I get a different exception.
den-run-ai commentedon Jun 11, 2017
DeclanHoare commentedon Jun 11, 2017
But... it doesn't have any instructions on what to do about it.
DeclanHoare commentedon Jun 11, 2017
Oh, I'm blind. Sorry.
DeclanHoare commentedon Jun 11, 2017
Okay, the library is working perfectly for me now. Thanks for your help. I'm not sure whether to close the issue or not, because of the issue with the NuGet package.
den-run-ai commentedon Jun 14, 2017
This is similar issue as this one:
#448
We can close this issue once next release is available.
filmor commentedon Nov 15, 2018
As this is apparently fixed on master, I'll close the issue.