Jason Grout wrote: > > Well, there is something to be said for what you said. We ship our own > version of matplotlib, which mostly likely is different than the system > install. That means that their perfectly good default matplotlibrc file > might cause deprecation warnings for us. For that reason, I think we > should still set the MATPLOTLIBRC environment variable to point to a > location within $DOT_SAGE. > > For that reason, how about yet another proposal: > > Add a warnings handler which traps the Matplotlib deprecation > warning. This handler will compare the matplotlibrc with the one that > was distributed in the last release (maybe by checking a hash value). > If it is identical (i.e., the user hasn't modified the matplotlibrc), > then *delete* the matplotlibrc. This is a > bit tricky, since the sage default matplotlibrc is not under version > control (it's in $SAGE_ROOT), so we don't know what older copies looked > like. (hehe...yet another reason to really like mabshoff for the > library of old builds). If the file is not identical to the current > sage default matplotlibrc, then throw a warning with a helpful error > message about updating the matplotlibrc (and where to find the file).
I should note that the file we would be deleting lives in $DOT_SAGE, and so should not affect the user's other usage of matplotlib outside of Sage. Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
