+lldb-dev since this could be useful to other people.
I’m actively working on getting Python 3.5 support working. If you want to go this route, it will make your life much easier. But I don’t have a fully passing test suite yet, there are still about 30 failing tests. So consider Python 3.5 experimental, and at your own risk. (Patches welcome!)
If you want to go with Python 2.7 then the test suite should pass fully, but there are 1-2 flaky timeouts that happen occasionally. But it is a lot more work to set up and nobody ever gets it right because it’s so complicated.
So, for Python 3.5:
- You must use Visual Studio 2015. 2013 or earlier will not work.
- Install Python 3.5 from python.org
- Run CMake with -DPYTHON_HOME=C:\Python35
- That’s it. You’re done.
You don’t need to build your own Python 3.5, which it sounds like what you’re doing. If you’re not trying to build your own Python 3.5, then check to make sure your PYTHONPATH is not set to anything. Mixed environments could be a problem. If that doesn’t fix it, then debugging into it a little bit could help. For example, try running C:\Python35\python_d.exe and then typing “import _ctypes”. It should work. If you’re doing a release build then try making sure that finish_swig is running python.exe, and if you’re doing a debug build then try making sure that finish_swig is running python_d.exe.
For Python 2.7
- You must not be using Visual Studio 2015. Only 2013 will work
- Can you tell me what command line you’re invoking CMake with?
- Can you open up build.ninja and search for this line:
Custom command for tools\lldb\CMakeFiles\finish_swig
And then paste the line under it back into this email?