Re: [MacPorts] #50058: Executables installed by pip are not linked into macports path (and are not “select”able in any way).

[MacPorts]

#50058: Executables installed by pip are not linked into macports path (and are not
“select”able in any way).
--------------------------+------------------------
  Reporter:  william@…    |      Owner:  stromnov@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  py-pip       |
--------------------------+------------------------

Comment (by hmijail@…):

 The "you can entirely break your macports installation" was scary, so I'd
 like to make sure that I got it right:

 One should NOT use pip to install packages on the macports directory tree
 (which is what a macports-installed pip would do by default!). The
 recommended procedure would be:
 * Install your python distribution and its pip (and probably its
 virtualenv)
 * Prepare a new place to install pip packages (like a virtualenv)
 * Use pip to install the packages into the new place

 A possible, but risky exception, would be: macports not carrying a pip-
 available package that has to be installed globally. It could then be
 installed into the macports directory tree, without fear of causing a
 conflict - until the day that macports *does* carry that package, and then
 the risk appears. Right?

 Is this documented somewhere? I'd say it should!

-- 
Ticket URL: <https://trac.macports.org/ticket/50058#comment:6>
MacPorts <https://www.macports.org/>
Ports system for OS X