Brian Granger wrote: >> This sounds great. However, what do we do about every sage install that >> exists out there right now? Every .sage directory already has a >> matplotlibrc file that throws warnings with the current matplotlibrc. >> Back when the decision was made, some ideas were kicked around: >> >> 1. Make a FAQ entry or documentation that upgrading to the next release >> requires a person to delete that file -- I think this is too hard to ask >> most people. >> >> 2. Every sage startup, check the DOT_SAGE directory to see if the >> matplotlibrc file there is identical to the file that we used to >> distribute and put in there. If it is, it is probably our original >> file, so just delete it. If it isn't, then someone modified it, so >> leave it. Put a FAQ entry in and something in the release notes to >> cover possible warnings experienced by people that modified their >> ./sage/matplotlibrc files. >> >> 3. Do option 2, but only do it for the next 6 months or something. >> After that, assume that everyone has cleaned up their .sage directory, >> so remove the check. >> >> What do people think? > > The existence of a $DOT_SAGE/matplotlibrc file won't affect the above > solution, > > export MPLCONFIGDIR=$DOT_SAGE/matplotlib > > in any way. By that, I mean that matplotlib will simply ignore the > old file because it won't be in the appointed config dir. The reason > for this is that previously, Sage didn't use MPLCONFIGDIR (which > points to the entire config directory), but rather MATPLOTLIBRC, which > just pointed to the rc file in the *top level* .sage directory. >
ah, right, I wasn't understanding your solution (for some reason, I thought you were using what we used before, not a new variable pointing to a new directory). +1 to your solution (I'd rather use your more standard directory name over William's non-standard name). Jason > What would be a problem is if Sage previously had created a > .sage/matplotlib/matplotlibrc file that no longer worked. But that > isn't the case. But Williams proposed name for the config dir > (matplotlibconfig) would also work fine. I would probably choose > "matplotlib" because that is the standard name that mpl uses, but it > doesn't really matter. > > Cheers, > > Brian > > > >> 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 -~----------~----~----~----~------~----~------~--~---
