MacPorts and Anaconda

[Ruben Di Battista]

This can be applied also to virtualenv. What you need to do, imho, is to
just create conda envs. They're isolated from system interpreters and they
should not collide with anything. In these envs you can install whatever
you want... And keep it from interfering with system packages...



On Mon, 12 Aug 2019, 07:55 Fielding, Eric J (US 329A) via macports-users, <
macports-users at lists.macports.org> wrote:

> I saw the discussion the last few days about the problems with using both
> HomeBrew and MacPorts on the same system. I was wondering about problems
> with using MacPorts and Anaconda to install different packages. I have been
> using MacPorts for a long time with few problems, but sometimes I need
> newer versions of Python packages or I need to install something that is
> available as a conda package. It seems that Anaconda is specifically
> designed to keep separate copies of the things it needs and switch between
> environments, so I assume that there should be fewer problems with MacPorts
> than using something like HomeBrew.
>
>
>
> Thanks,
>
>                 ++Eric
>
> Pasadena, California
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20190812/0ede537f/attachment.html>