![]() Idle3.5 -> /opt/local/Library/Frameworks/amework/Versions/3.5/bin/idle3.5 Idle3.4 -> /opt/local/Library/Frameworks/amework/Versions/3.4/bin/idle3.4 Idle2.7 -> /opt/local/Library/Frameworks/amework/Versions/2.7/bin/idle2.7 There's clearly some precedent for linking binaries to do with a specific python version directly in this way, since for example idle is linked thus on my installation, so the desired end result (I end up with a link /opt/local/bin/aws -> /opt/local/Library/Frameworks/amework/Versions/3.5/bin/aws) would be consistent with this: This puts the question firmly in MacPorts' world, as per the latest comments on the github issue.īeporter's comment (third from last in that github issue at the time of writing) echos my feeling here … I would expect that something installed with the currently selected version of pip would end up on my path, though I completely understand why it doesn't at present. There follows the question of how to achieve this, since standard pip doesn't know it's supposed to do something about any binaries installed /after/ the port select operation, other than to install them in the appropriate place in the python heirarchy for the selected version of pip. ![]() Of course that doean't happen with a standard pip. I would naively expect at first glance that issuing a sudo port select pip pip35 would cause any binaries subsequently installed by that version of pip to be linked into my macports path /opt/local/bin. The problem is that that path is not on my PATH (of course … port select can't alter my path, only the individual symlinks in /opt/local/bin to the objects which are owned by that particular port for which port select was run). The aws binary is installed by pip at /opt/local/Library/Frameworks/amework/Versions/3.5/bin/aws. I then used pip to install the aws cli tools, sudo pip install aws. In my example, I have installed macports' pip, and have port selected python35 and pip35. In short: when I install a python package using pip, its executables are installed into the appropriately versioned python tree, but those executables are not symlinked to somewhere which is on my PATH. There's some prior discussion of this problem at
0 Comments
Leave a Reply. |