That sounds fair, we should definitely make sure we're on the same
page. I've put up D34872 to better document state of affairs after the
recent refactors.
I am a bit reluctant to try to document the "direction we're heading
towards" because that is something where I am still developing
clarity, a
Python support on Windows is much more problematic than support on something
like MacOS or Linux. The python you use when you run lldb must be the same
python used when you build it. Bad things happen – warnings, crashes, etc –
when you use a different rev of the dll/so or the library directory
On Fri, Jun 30, 2017 at 12:39 PM Ted Woodward via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Python support on Windows is much more problematic than support on
> something like MacOS or Linux. The python you use when you run lldb must be
> the same python used when you build it. Bad things happe
I’ve seen crashes on Linux when building with 2.7.6 and using the 2.7.3
.so/library directory, so I’m not willing to say building on Windows with 3.6.1
and using the 3.5.2 dll/library directory will work. Python has never been very
forgiving when using a different setup than what you built with.
On Fri, Jun 30, 2017 at 1:34 PM Ted Woodward
wrote:
> I’ve seen crashes on Linux when building with 2.7.6 and using the 2.7.3
> .so/library directory, so I’m not willing to say building on Windows with
> 3.6.1 and using the 3.5.2 dll/library directory will work. Python has never
> been very forgi
Note that building with 3.6.x and using 3.5.x won't work, but any of 3.5.x
revisions should be compatible between themselves.
On Fri, Jun 30, 2017 at 1:41 PM, Zachary Turner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
>
>
> On Fri, Jun 30, 2017 at 1:34 PM Ted Woodward
> wrote:
>
>> I’ve seen
