I am still having the same problem with PyPlot. I couldn't get it to work in .3.10 for more than one session, before it broke.
LoadError: LoadError: InitError: Failed to pyimport("matplotlib"): PyPlot will not work until you have a functioning matplotlib module. PyError (:PyImport_ImportModule) <type 'exceptions.ImportError'> ImportError('cannot import name scimath',) File "/home/tommy/anaconda/lib/python2.7/site-packages/matplotlib/__init__.py", line 180, in <module> from matplotlib.cbook import is_string_like File "/home/tommy/anaconda/lib/python2.7/site-packages/matplotlib/cbook.py", line 33, in <module> import numpy as np File "/home/tommy/anaconda/lib/python2.7/site-packages/numpy/__init__.py", line 170, in <module> from . import add_newdocs File "/home/tommy/anaconda/lib/python2.7/site-packages/numpy/add_newdocs.py", line 13, in <module> from numpy.lib import add_newdoc File "/home/tommy/anaconda/lib/python2.7/site-packages/numpy/lib/__init__.py", line 17, in <module> from . import scimath as emath during initialization of module PyPlot while loading /home/tommy/.julia/v0.4/PyPlot/src/PyPlot.jl, in expression starting on line 653 while loading In[2], in expression starting on line 1 in __init__ at /home/tommy/.julia/v0.4/PyPlot/src/PyPlot.jl:232 in include at ./boot.jl:260 in include_from_node1 at ./loading.jl:271 in require at ./loading.jl:210 On Thursday, September 10, 2015 at 2:20:30 PM UTC-4, Uwe Fechner wrote: > > This is not yet fixed. > > I deleted .jula/v0.4/PyCall and .jula/v0.4/PyPlot. > Then I did: > Pkg.update() > Pkg.checkout("PyCall") > Pkg.checkout("PyPlot") > Pkg.build("PyCall") > using PyPlot > > This works fine. But if I restart Julia > and do using PyPlot again, I get the error: > > julia> tic(); using PyPlot; toc(); > /home/ufechner/miniconda/envs/kitepower/lib/python2.7/site-packages/matplotlib/__init__.py:1155: > > UserWarning: This call to matplotlib.use() has no effect > because the backend has already been chosen; > matplotlib.use() must be called *before* pylab, matplotlib.pyplot, > or matplotlib.backends is imported for the first time. > > warnings.warn(_use_error_msg) > ERROR: LoadError: InitError: PyError (:PyImport_ImportModule) <type > 'exceptions.ImportError'> > ImportError('/home/ufechner/miniconda/envs/kitepower/lib/python2.7/site-packages/sip.so: > > undefined symbol: PyProperty_Type',) > File > "/home/ufechner/miniconda/envs/kitepower/lib/python2.7/site-packages/matplotlib/pyplot.py", > > line 98, in <module> > _backend_mod, new_figure_manager, draw_if_interactive, _show = > pylab_setup() > File > "/home/ufechner/miniconda/envs/kitepower/lib/python2.7/site-packages/matplotlib/backends/__init__.py", > > line 28, in pylab_setup > globals(),locals(),[backend_name],0) > File > "/home/ufechner/miniconda/envs/kitepower/lib/python2.7/site-packages/matplotlib/backends/backend_qt4agg.py", > > line 13, in <module> > from backend_qt4 import QtCore, QtGui, FigureManagerQT, > FigureCanvasQT,\ > File > "/home/ufechner/miniconda/envs/kitepower/lib/python2.7/site-packages/matplotlib/backends/backend_qt4.py", > > line 25, in <module> > from qt4_compat import QtCore, QtGui, _getSaveFileName, __version__ > File > "/home/ufechner/miniconda/envs/kitepower/lib/python2.7/site-packages/matplotlib/backends/qt4_compat.py", > > line 36, in <module> > import sip > > [inlined code] from /home/ufechner/.julia/v0.4/PyCall/src/exception.jl:82 > in pyimport at /home/ufechner/.julia/v0.4/PyCall/src/PyCall.jl:315 > in __init__ at /home/ufechner/.julia/v0.4/PyPlot/src/PyPlot.jl:245 > in include at ./boot.jl:260 > in include_from_node1 at ./loading.jl:271 > in require at ./loading.jl:210 > during initialization of module PyPlot > while loading /home/ufechner/.julia/v0.4/PyPlot/src/PyPlot.jl, in > expression starting on line 653 > > Any idea? > > Uwe Fechner > > > Am Donnerstag, 10. September 2015 18:51:32 UTC+2 schrieb Steven G. Johnson: >> >> Just merged a fix, I think. >> >> I've fallen behind a bit on PyCall and PyPlot issues, but I'll be >> cleaning things up over the next few days since I need these for my class >> soon. >> >