Hi Eric I tried the new spy function under Windows and it seemed to work OK. A great leap forward, actually, given the problems I had been seeing. Merging the spy functions was a good idea (does it work ok for very very large, very sparse matrices?)
Trying it under Ubuntu was less straightforward. I built an RPM (python setup.py bdist_rpm) then converted it to deb package then installed it. It complained about my old ~/.matplotlib/matplotlibrc file so I moved it out of the way. Then I fired up again and it was OK. In my new Ubuntu install of matplotlib, sans matplotlibrc, I would like to switch GUIs to GTKAgg but there doesn't seem to be a /etc/matplotlibrc file from which to base my configuration. Is this a fault of my rpm-to-deb process, or something that failed during build? Is it still possible to run the GTKAgg GUI? Has the config system changed? Finally, can I suggest that the website be updated with some information about the new release? I couldn't find any readable information about it on-line -- had to go to the tarball. I think generally the matplotlib community would benefit from more frequently updated website. While I'm at it, maybe I could suggest a matplotlib wiki that gets a bit more prominance on the homepage and that is *separate* from the scipy one, since the scipy wiki gives completely mixed messages about what plotting engine is preferred (chaco.wx and VTK and so on) -- it can't be helping the matplotlib cause. http://matplotlib.sourceforge.net/whats_new.html (bit out of date) Cheers JP Eric Firing wrote: > > John Pye wrote: > >> >> Hi all >> >> >> >> I have got some funny behaviour here that looks like a bug with the >> >> spy() function. Using the latest python-matplotlib 0.87.5 package on >> >> Ubuntu 6.10, I try: >> >> >> >> $ ipython -pylab >> >> from scipy import io >> >> M = io.mmread('gd.mm') >> >> spy(M) >> >> M.shape >> >> M.nnz >> >> >> >> It looks great and I get the necessary number of dots on my 'spy' plot. >> >> Then: >> >> >> >> spy(M.todense()) >> >> >> >> This seems to plot only half of the points. At first I thought the >> >> 'todense' function must be to blame, however: >> >> >> >> D = M.todense() >> >> for i in range(0,231): >> >> for j in range(0,231): >> >> if D[i,j]: >> >> print i,j,D[i,j] >> >> >> >> gave me the right data, so it really looks like a bug with spy(). >> >> >> >> And FWIW spy2(M) fails with an error, whereas spy2(D) shows the same bug >> >> as spy(D). >> >> >> >> Is this something that has been fixed in the new 0.90 release? >> > > > > The two versions of spy were merged into one, with some rewriting, in > > 0.90. Please give it a try and see if the problem persists. > > > > Eric > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
