Andrew Straw wrote: > Hi Eric, > > show() isn't bringing up my plots with r5430 in normal scripts (i.e. not > using IPython).
Sure enough. It seems that in the process of bisecting the svn versions to track down this problem and the original one you reported, things got mixed up in my directory, so that what worked on what I thought was the svn head was actually working on some mongrel. After a fresh checkout with clean build and install, I find that neither plain show nor ipython -pylab is working. Back to the drawing board. I really would like to get everything working with complete case-insensitivity, and lower-case defaults, for the backend names. There is no reason one should have to remember that it is TkAgg, not TKAgg, but GTKAgg, not GtkAgg. Eric > > -Andrew > > Eric Firing wrote: >> While investigating a bug pointed out by Andrew (and one that I had >> introduced some time ago) I found to my horror that I had also caused >> another bug: interactive plotting was not working with ipython -pylab. >> I backed out part of r5420, and that fixed the problem. This temporary >> fix is to restore the mixed case backend names in the interactive_bk >> list that is now set in rcsetup.py and imported by backends/__init__.py. >> >> I am baffled as to why this is needed at present; I have not been able >> to figure out why ipython threading seems to get confused when that list >> has lower case names for gtkagg, qtagg, and wxagg, but not for tkagg or >> qt4agg. I don't see anywhere in either the ipython or the mpl code that >> should care about the case of the names in that list, now that I have >> ensured that comparisons against backend names in mpl (everywhere I >> could find them--maybe I missed on) are case-insensitive, and >> get_backend() returns only lower case. rcParams['backend'] can still >> have mixed case, however. >> >> Any suggestions as to what I am missing or where to look? >> >> Related question: I just noticed that there is also a config/rcsetup.py. >> Is there any reason why there has to be so much duplication (and now >> gradual divergence) between this and the regular rcsetup.py? Is there >> any reason the traits config system can't use the regular version, maybe >> with some changes merged in? >> >> Eric >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
