[lug] compatibility (not even backward!) issues

[Bear Giles]

It's at an entirely different level but one of my current headaches is that
we're still using a single uber-dev environment and 'yarn' can mean:

- nodejs package manager
- hadoop CLI application

I need both. Fortunately not at the same time but it's a real headache
because of the package dependencies when you need to remove one before
installing the other.

On Thu, Sep 17, 2020 at 6:42 AM Davide Del Vento <davide.del.vento at gmail.com>
wrote:

> On Thu, Sep 17, 2020 at 6:35 AM Davide Del Vento <
> davide.del.vento at gmail.com> wrote
>
>> Things that bug me are others, like... let me start a new thread instead
>> of hijacking this one...
>>
>
> In case you haven't seen this one, it's pretty.... interesting (make sure
> you check what the maintainers of the other packages said). This is a
> serious issue of "present" compatibility which can be solved only breaking
> backward compatibility until someone picks a name someone else already
> picked and it breaks again: https://github.com/pypa/pip/issues/4625
>
> Well, hopefully https://github.com/pypa/pip/issues/988 will solve it, but
> it's only 7 years old, so don't hold your breath. And perhaps it's out of
> scope....
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20200917/c4209831/attachment.html>