Re: [MacPorts] #50058: Executables installed by pip are not linked into macports path (and are not “select”able in any way).
MacPorts
noreply at macports.org
Tue Apr 9 23:36:15 UTC 2024
#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 fmw42):
Ryan,
Thanks for you answer.
News to me that MacPorts now supports Imagemagick 7. When did that
happen?
But what if I need an Imagemagick delegate that is not currently installed
with Imagemagick? The downside is that I have to wait for MacPorts to
update Imagemagick whose release often is upgraded weekly (and I do
testing and answer Imagemagick questions, so need to be current). That
was why I installed via source but use MacPorts to get my delegates.
If I use MacPorts pip to install Python related tools, but use MacPorts
for my Imagemagick delegates, then I would have duplicates of a number of
things. That was what I wanted to try to avoid. That would happen whether
I would use MacPorts Pip or Pip installed for my Mac Python if I want to
continue installing Imagemagick from source with MacPorts delegates. Is
my logic correct? Or is there some way to have only one set.
--
Ticket URL: <https://trac.macports.org/ticket/50058#comment:20>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list