Brian Granger wrote: >> I want to reopen this thread. > > Great! matplotlib under Sage is still broken for me because of this > issue - I would love to see this resolved. > >> I have a build farm with many (nearly 20) different OS's that all build and >> test >> Sage in parallel. My home directory on each of those machines is NFS >> exported >> and shared. I sometimes have tests fail because all these different >> Sage's are trying to write to the same $HOME/.matplotlib directory >> (for temp files, configuration, etc.). >> For Sage itself, I set SAGE_HOME to a fast local scratch disk (on each >> machine), which completely solves any contention problems for >> *everything* related to Sage temp files, configuration, etc., with the >> notable exception of matplotlib. > > I hadn't thought of this issue, but it is another good reason to not > use $HOME/.matplotlib for the Sage matplotlib. > >> Thus I would also prefer it if >> Sage's matplotlib directory were under SAGE_HOME instead of it being >> the default $HOME/.matplotlib. >> >> Thoughts? > > I think the simplest solution is to have Sage set: > > export MPLCONFIGDIR=$SAGE_HOME/matplotlib > > But, wait, does SAGE_HOME point to $HOME/.sage by default? That is > the right place for this, I just don't remember exactly where > SAGE_HOME points. > > I don't even think we need to put a default matplotlibrc file there, > so we don't have to worry about it becoming out of date. If people > want to add their own matplotlibrc file to this directory they can, > but the default will be that matplotlib works.
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? 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 -~----------~----~----~----~------~----~------~--~---
