Re: [lldb-dev] Redundant six.py copy

2016-05-01 Thread Kamil Rytarowski via lldb-dev
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-

Re: [lldb-dev] Redundant six.py copy

2016-05-01 Thread Zachary Turner via lldb-dev
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,

[lldb-dev] Redundant six.py copy

2016-05-01 Thread Kamil Rytarowski via lldb-dev
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 version shipped with a system? Alternatively are there plans to migrate to Python 3 and remove need for i