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 in their systems with their python installations? [1] http://pkgsrc.se/dependon.php?path=lang/py-six&branch=CURRENT On 02.05.2016 00:35, Zachary Turner wrote: > 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, so it will continue to be > needed. Do you actually get an error? > On Sun, May 1, 2016 at 2:22 PM Kamil Rytarowski via lldb-dev > <lldb-dev@lists.llvm.org <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 > 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 it? > > How to address this conflict cleanly? > > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org <mailto:lldb-dev@lists.llvm.org> > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev