> -Original Message-
> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Pavel
> Labath via lldb-dev
> Sent: Tuesday, May 03, 2016 4:01 AM
> To: Kamil Rytarowski
> Cc: LLDB
> Subject: Re: [lldb-dev] Redundant six.py copy
>
> We could have a cmake option,
m, a
>>> Linux Foundation Collaborative Project
>>>
>>>> -Original Message-
>>>> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Kamil
>>>> Rytarowski via lldb-dev
>>>> Sent: Monday, May 02, 2016 4:36 PM
>>
vm.org] On Behalf Of Kamil
>>> Rytarowski via lldb-dev
>>> Sent: Monday, May 02, 2016 4:36 PM
>>> To: Reid Kleckner
>>> Cc: LLDB
>>> Subject: Re: [lldb-dev] Redundant six.py copy
>>>
>>>
>>>
>>> On 02.05.2016 18
l Message-
>> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Kamil
>> Rytarowski via lldb-dev
>> Sent: Monday, May 02, 2016 4:36 PM
>> To: Reid Kleckner
>> Cc: LLDB
>> Subject: Re: [lldb-dev] Redundant six.py copy
>>
>>
>
[mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Kamil
> Rytarowski via lldb-dev
> Sent: Monday, May 02, 2016 4:36 PM
> To: Reid Kleckner
> Cc: LLDB
> Subject: Re: [lldb-dev] Redundant six.py copy
>
>
>
> On 02.05.2016 18:40, Reid Kleckner wrote:
> > On
On 02.05.2016 18:40, Reid Kleckner wrote:
> On Sun, May 1, 2016 at 2:21 PM, Kamil Rytarowski via lldb-dev
> mailto:lldb-dev@lists.llvm.org>> wrote:
>
> It has been noted that LLDB installs its own copy of six.py
> (third_party/Python/module/six/six.py) that conflicts with a
standalone
>
On Sun, May 1, 2016 at 2:21 PM, Kamil Rytarowski via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> It has been noted that LLDB installs its own copy of six.py
> (third_party/Python/module/six/six.py) that conflicts with a standalone
> one lang/py-six (path in pkgsrc).
>
> Could we reuse an external
There are currently 83 packages that require py-six in pkgsrc [1] and
changes for a conflict are high, unless someone is using a bare system
with a minimal set of packages.
I'm looking for a solution that is applicable upstream and isn't
patching the sources downstream. Can other users install py-
Six isn't a module that is normally installed. I think the pythonic way to
do this is tell people "you need to install six before you can use lldb",
but given the number of different ways in which people use it and the
different needs, this isn't ideal.
There are no plans to drop support for 2.7,
