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 william@…):

 Replying to [comment:3 stromnov@…]:
 > So, it's preferably to install custom packages into separate dirs, or
 install custom packages using macports build system.

 I guess the “correct” response to the absence of a given package in
 macports is to request that it be added then (e.g. I might want there to
 exist a package py35-awscli (purely theoretically ;), in which case I
 should request that new port. It seems a pity not to be able to use the
 pip infrastructure in a more synergistic way with macports, but I guess we
 are where we are!

 This does ask the rather more serious question though: if it's bad
 practice to install packages in macports python using pip, why does
 macports provide a port of pip? That's a discussion for another day
 though!

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