When we move to VS 2015 (which will be soon, btw) we will require Python 3.5+ on Windows. This already works for the most part, you can even try it out today. I've spent the better part of the past 6 months making LLDB's python bindings work with Python 3. The best part is that you don't need to custom build Python 3.5, you can just use the installer from Python.org (make sure you choose to install debug binaries too).
So in summary: * VS 2013 -> requires Python custom built version of Python 2.7 * VS 2015 -> requires any version of Python >= 3.5, doesn't have to be custom built. On Thu, Jan 14, 2016 at 10:20 AM Vadim Chugunov via lldb-dev < lldb-dev@lists.llvm.org> wrote: > VS 2013 support is going to be deprecated soon. At that point it could > > break any time, because nobody is going to be making an effort to keep it >> > working. >> > How is this going to play with Python scripting on Windows? Given that LLDB > only supports Python 2.7 bindings, > and that Python 2.7 extensions can be built only with VS2008, isn't that > going to be a problem? > (When LLDB for Windows is officially declared "ready", that is. For now, one > can rebuild Python with VS2015.) > > Vadim > > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
