First off, good point, and thank you for PyPlot and PyCall. I use these packages a ton.
But loading PyPlot is by far the slowest part of my code currently. Maybe that will go away with module caching? I was, perhaps incorrectly, thinking it was slow because it was Python. Also passing stuff to Python is not always trivial. I wasn't able to successfully plot masked arrays using PyPlot, for example. I'm sure it can be done, but it was too complicated for me to figure out for too little gain. On Wednesday, December 17, 2014 12:00:59 PM UTC-6, Steven G. Johnson wrote: > > > > On Tuesday, December 16, 2014 4:15:42 PM UTC-5, David Smith wrote: >> >> My biggest wish-list item (as a medical imager) would be native Julia >> plotting that is similar to Matplotlib. I'd rather not have to require >> that people have Python alongside Julia. Makes Julia sound less mature. >> > > Julia *is* significantly less mature than Python, and for the next several > years (at least!) there will undoubtedly be lots of major functionality > that is available in Python but not in pure Julia. Fortunately, pretty > much all of this functionality is accessible via PyCall. > > As a result, I pretty much always strongly recommend that people using > Julia also have a decent Python/SciPy installation (I recommend Anaconda on > Windows and Mac). This is also needed if you want to use IJulia. > > I don't think we should be any more ashamed of calling Python for things > like plotting than we are ashamed of calling C and Fortran code for linear > algebra or Bessel functions. > > --SGJ >
