[lldb-dev] RFC: Separation of embedded Python from the rest of LLDB.

[Mukul Sabharwal]

I'd like to also add my support to solution #1.

My use case is literally what Zachary has outlined -- Building on Windows,
wanting to interface with LLDB not using Python but a different language,
say C#.

The Python requirement (and that too building from source) was a bit of an
odd (for a non-Python user) step and probably the biggest impediment to
getting started.

I'm all for language interop, but this special treatment Python is getting
in the LLDB project will accrue (and I'd argue already is) long-term
technical debt.


On Wed, Feb 25, 2015 at 8:58 AM, Reid Kleckner <rnk at google.com> wrote:

> On Wed, Feb 25, 2015 at 5:58 AM, Vince Harron <vharron at google.com> wrote:
>
>> This seems like a lot of work to support Windows users who might want to
>> use pre-compiled python modules.
>>
>
> To me, the primary benefit is that you can build LLDB with Python support
> without building Python from source. More onerous, once you build Python
> from source, you have to maintain two separate environments: your normal
> development environment with normal Python on PATH, and one with LLDB's
> version of Python on PATH and PYTHONPATH.
>
>
>> I think we should distribute a VS2015 based version of Python 2.7
>> binaries and call it a day.
>>
>> We can worry about 2020 problems in 2020.  =)
>>
>> Reasonable people may disagree.
>>
>
> I disagree. I guess that makes me reasonable. ;)
>
> The main thing for me is that once we put together a pre-built Python, the
> instructions to rebuild it will immediately rot. In a matter of months,
> some user will arrive needing LLDB and Python to be built with a different
> VS version, and I give it 50/50 odds that the instructions will work.
>
> Personally, I think the lowest impact change for everyone not affected by
> this is to split the Python API code out into a shared library. LLDB has
> more Python source than C++ source interacting with Python. Maintaining
> Python source compat with 2.7 and 3.5 will be fragile and will require
> testing more configurations. Reducing the number of obscure ways that
> non-Windows developers can break the Windows build is good.
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150225/ca94ec76/attachment.html>