> On May 1, 2020, at 8:14 AM, Christopher Jones <[email protected]>
> wrote:
>
> As an end user you should not use pip, any version of it, to install packages
> directly into the MacPorts prefix. period.
>
> As previously noted, you can though use it for instance inside a virtual env.
> that is just fine.
>
> ( Also, the macports pip package is also there to help certain macports ports
> internally on how they build themselves, and install into the macports
> prefix. )
If you don't want to mess around with virtual envs, you can simply "pip install
--user", which writes to ~/Library/Python/.... You do need to add
~/Library/Python/3.8/bin
(assuming python 3.8) to your PATH, but the corresponding python module path is
automagically used by python. I typically either use macports to install the
macport-ified python package, or pip as above.
Noam