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:  gallafent    |      Owner:  stromnov
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  py-pip       |
--------------------------+----------------------

Comment (by hmijail):

 Replying to [comment:19 ryandesign]:

 > Horacio, I can't speak for Homebrew or the contents of the article you
 linked to, but MacPorts ports, including pythons, ''are'' (''of course'')
 intended for use by users. There's no need to install a separate copy of
 python outside of MacPorts that you then have to separately remember to
 update.

 Ryan, my comment was informed in part by the fact that I also commented in
 this very same issue 8 years ago with my difficulties (see comment:6). My
 comment never got addressed. Eventually I dealt with it, because
 fortunately I can debug stuff myself.

 I appreciate MacPorts wants to be used by Python users - would be nice. I
 wonder what it does better than Homebrew for that to make sense. 8 years
 later, that guide for beginners still resonates too much. I am not trying
 again, and personally I'm not recommending others they do.

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