![]() Since this happens with _io, this looks like a bug in python 2.7.11 (unlikely, there would be a world-scale outcry and a prompt fix if it was) or some packaging bug or version mismatch specifically with the homebrew version (and maybe some related ones, too). CELLAR MACVIM INSTALLIf you are using conda package control, simply run “conda install CELLAR MACVIM UPDATEYou do not have custom PYTHON_PATH, uninstall python, uninstall vim.Ĭulprit is the update from python 2.7.10 to 2.7.11. Workaround was simple: open new terminal, make sure that Set to one of my dev environments, where I also had some libraries, Python and vim with homebrew, when PYTHON_PATH has been specified and I had the same issue, but successfully fixed. Maybe somehow merely calling python invokes some strange mix of the 2.7.11 executable with the 2.7.10 dylibs? So, as a workaround, you can try doing the same thing.Įlsewhere, I’ve posted a separate question about this puzzling behavior. In /Library/Frameworks/amework/Versions/ 2.7/lib/python2. Referenced from: /Library/Frameworks/amework/Versions/ 2.7/lib/python2. 7/lib-dynload/_io.so, 2): Symbol not found: _P圜odecInfo_GetIncrementalDecoder ImportError: dlopen(/Library/Frameworks/amework/Versions/ 2.7/lib/python2. … but this doesn’t: $ python -c "import io"įile "/Library/Frameworks/amework/Versions/2.7/lib/python2.7/io.py", line 51, in CELLAR MACVIM FULLSo, for me, this works (invoking python via the full path /usr/local/bin/python): $ which python Strangely, the issue seems to be related to some subtle difference between how OSX launches python when I invoke it from the shell using the full path vs. I installed python 2.7.11 via an installer from. This means that the old executable was running, but the new sys.executable value caused all the wrong modules to get loaded (including the io module). So, the old executable was called, but the new path was provided to python in sys.argv. But bash was still using the old cache location /usr/bin/python. In my case, I was typing python, which was on my $PATH at /usr/local/bin/python. ![]() When you install a new version of python, you may need to run hash -r python to tell bash to reset the “cached” location to the python executable. Tl dr: Fix this issue by doing one of the following:ĮDIT: An answer to my related question makes it clear what’s happening here. If I do it directly at the system command line (Terminal on OS X) I have no problems. I only get this issue if I execute from within my IDE’s console. 11/Frameworks/amework/Versions/ 2.7/lib/python2. Referenced from: /usr/local/Cellar/python/ 2.7. ImportError: dlopen(/usr/local/Cellar/python/ 2.7. I now get Traceback (most recent call last):įile "/usr/local/lib/python2.7/site-packages/setuptools/_init_.py", line 12, in įrom setuptools.extension import Extensionįile "/usr/local/lib/python2.7/site-packages/setuptools/extension.py", line 8, in įile "/usr/local/lib/python2.7/site-packages/setuptools/dist.py", line 16, in įile "/usr/local/lib/python2.7/site-packages/setuptools/depends.py", line 6, in įile "/usr/local/lib/python2.7/site-packages/setuptools/compat.py", line 17, in įile "/usr/local/Cellar/python/2.7.11/Frameworks/amework/Versions/2.7/lib/python2.7/httplib.py", line 80, in įile "/usr/local/Cellar/python/2.7.11/Frameworks/amework/Versions/2.7/lib/python2.7/mimetools.py", line 6, in įile "/usr/local/Cellar/python/2.7.11/Frameworks/amework/Versions/2.7/lib/python2.7/tempfile.py", line 32, in įile "/usr/local/Cellar/python/2.7.11/Frameworks/amework/Versions/2.7/lib/python2.7/io.py", line 51, in Running (as an “External Tool”) python -B setup.py register -r pypitest Since updating from Homebrew Python 2.7.11 (from 2.7.10) I’m suddenly unable to test register my package on PyPi from the P圜harm IDE console. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |