On Jan 29, 2008 7:41 PM, William Stein <[EMAIL PROTECTED]> wrote: > > On Jan 29, 2008 7:08 PM, alex clemesha <[EMAIL PROTECTED]> wrote: > > Update: > > > > Uh, so I just did > > > > rm -rf ~/.matplotlib > > > > and then restarted Sage and now the plotting is working. > > > > So I don't know what to say about that except ahhhhh > > ... but I guess all is well now? > > This is a common problem with the design of the > matplotlib config file, which has caused > confusion over the years. I don't like how it is designed > to just randomly fail when one upgrades matplotlib (which Sage > did recently). I wish it would fail more gracefully. > > I know -- "shut up and show me the code"...
No need to, it's been done. This is a known and annoying problem, and I recently wrote some code in ipython to provide a different config mechanism that would also help with this issue: http://projects.scipy.org/ipython/ipython/browser/ipython1/trunk/sandbox/tconfig The mpl team hasn't made it the default yet, but it's already an option for mpl, and may become the default system after more testing. When working on it, one of the things I discussed most with John Hunter was precisely how to make a system that would be more robust across upgrades and that would make it easier to provide graceful fallbacks. Cheers, f --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
