QtCore.so: Reason Image Not Found -> Library not loaded: @rpath/libpyside.cpython-34m.1.2.dylib

I am getting the following running pycharm on my mac - sierra osx

 

/Users/MyName/tensorflow/bin/python /Applications/PyCharm.app/Contents/helpers/pydev/pydevd.py --multiproc --qt-support --client 127.0.0.1 --port 61975 --file /Users/MyName/Desktop/Appraisals/learning_recipes/hello_world_v2.py
warning: Debugger speedups using cython not found. Run '"/Users/MyName/tensorflow/bin/python" "/Applications/PyCharm.app/Contents/helpers/pydev/setup_cython.py" build_ext --inplace' to build.
pydev debugger: process 20990 is connecting

Traceback (most recent call last):
File "/Applications/PyCharm.app/Contents/helpers/pydev/pydevd.py", line 1567, in <module>
apply_debugger_options(setup)
File "/Applications/PyCharm.app/Contents/helpers/pydev/pydevd.py", line 1401, in apply_debugger_options
enable_qt_support(setup_options['qt-support'])
File "/Applications/PyCharm.app/Contents/helpers/pydev/pydevd.py", line 1065, in enable_qt_support
pydev_monkey_qt.patch_qt(qt_support_mode)
File "/Applications/PyCharm.app/Contents/helpers/pydev/_pydev_bundle/pydev_monkey_qt.py", line 49, in patch_qt
import PySide.QtCore # @UnresolvedImport
ImportError: dlopen(/Users/MyName/tensorflow/lib/python3.4/site-packages/PySide/QtCore.so, 2): Library not loaded: @rpath/libpyside.cpython-34m.1.2.dylib
Referenced from: /Users/MyName/tensorflow/lib/python3.4/site-packages/PySide/QtCore.so
Reason: image not found

Process finished with exit code 1

 

I am trying to debug a problem with dot/pydotplus/graphvis with python3 under a virtualenv i setup.  But when trying to setup pycharm i am getting the above error when i run debug on my script.  I had installed an earlier versoin of pycharm on my mac under a earlier osx and without a virtualenv and it seemed to work fine.  I have not really much experience with virtualenv and in some ways scripting/programing on a mac is not that familiar also.  So any help would be greatly appreciated.

I figure it is something to do with the way the virtualenv is setting up the paths to the dylib, but I have no idea how to fix it...

Thanks.  

Please sign in to leave a comment.