![macports python pip macports python pip](https://biggles-plot.github.io/examples/example1.png)
#Macports python pip mac
I have learned from painful experience to use Mac Ports distributed python packages and not the ones from Apple or even from. General consensus is that you should not dork with Apple's frameworks. which would explain my problems with venvs both pre- and post python v3.3.Īdmittedly, Macs are weird in that Apple installs its python framework in one place while Mac Ports installs its ports of Python elsewhere. So, maybe, the Mac Ports virtualenv port is smart enough to know, in the wacky world of Apple, to use the Mac Ports installed pip rather than the one from somewhere in the Apple installed framework that P圜harm and pyenv use. Browsing the lib folders for the venvs using Finder confirms that Packages is reading what really was installed. It is only for the virtualenv created venv that Packages correctly shows the latest pip v1.2.1 as what is being used. The weird thing is that if I open a term session, cd into the bin folder of that venv, then enter python, IDLE confirms that Python loaded and I can enter 'import sympy, numpy' and then 'help(s)' and those two statements execute as expected.Ī disturbing aspect of this is that the Packages tab for the P圜harm created venv lists pip v1.1 as the one being used. But, after Reload completed without any error message, and I switched back to the Packages tab, sympy and numpy were not listed. Just tried that on a venv I created with P圜harm rather than from a term session using pyenv or virtualenv. P圜harm will only see those packages if the venv was created using Mac Ports' p圓3-virtualenv port.Īnd, yes, I do use the –system-site-packages switch when creating venvs from a term session.
#Macports python pip install
Alas, not only has nothing changed, but even if I create a venv using python v3.3's pyenv from a term session, and then install Mac Ports numpy and sympy packages, P圜harm still does not see those packages. Nevertheless, since Python v3.3 now has a built-in alternative to virtualenv which P圜harm's Project Interpreter uses, I decided to revisit the problem. It is not that big a deal to create venvs with virtualenv from a term session, and install packages with Mac Ports instead of P圜harms' Install feature, so I can live with the Way things are. My experience is that Mac Ports packages are more compatible with my Mac than the ones that PIP pulls down. A workaround I discovered was, since I use a Mac and since I have Mac Ports installed, to install the Mac Ports version of whatever package I wanted to a virtual env created not by using P圜harm's Project Interpreter Preferences but by using the Mac Ports port of virtualenv instead. When such problems occurred, it was a no-go whether P圜harm's PI was a virtual env or not. In the past, I have found I was not able to install some or all of these packages using the Install feature of P圜harm's Project Interpreter Preferences. I even tried adding /opt/local/Library/Frameworks/amework/Versions/2.7/lib/python2.7/site-packagesīut the executables are not found on the command line, even though the packages work perfectly from within python.I should start with the disclaimer that I am running Snow Leopard on my Mac.
![macports python pip macports python pip](https://upload-images.jianshu.io/upload_images/8034195-338f47c57e80b3ca.png)
I get this for any package installed using pip on my computer. It gives an error : "sudo: rosdep: command not found" However if I try to run : sudo rosdep init, Which installs without errors and corresponding files are located in /opt/local/Library/Frameworks/amework/Versions/2.7/lib/python2.7/site-packages However any executable associated with a package that can be called from the command line in the terminal are not found.ĭoes anyone know what might be wrong? (More details below)įor example while installing a package called "rosdep" as instructed in I can successfully install packages and import them inside my python environment and python scripts. I installed python2.7 and pip using macport as done in
#Macports python pip mac os x
I am working on mac OS X Yosemite, version 10.10.3.