Brian Granger wrote: >> Details are here: http://trac.sagemath.org/sage_trac/ticket/4774 > > I have skimmed though this as well as the previous thread on this > topic. But, it still seems like the original problem remains (Sage's > matplotlib using the wrong matplotlibrc) even though Sage no longer > includes its own matplotlibrc. Even if Sage doesn't include its own > matplotlibrc, it should take steps (such as setting MPLCONFIGDIR) to > prevent another and wrong matplotlibrc from being used. Otherwise > Sage won't work for any user that already has a custom matplotlibrc > installed. Or is there another recommended way of resolving this that > I am missing?
I agree that there still is a problem. Before, I didn't think that Sage's matplotlib would need to have different options to even be able to function. In the mailing list thread, the option was brought up to have the user put in a command in their init.sage file if they wanted a custom Sage initialization for matplotlib. Setting the MATPLOTLIBRC variable in the init.sage file should work, I think. In reality, (I think) the people this affects are the people that have already customized their system install of matplotlib. Those are the people that (I think) would be capable of writing another command in their init.sage or something to have Sage have a custom matplotlibrc file. On the other hand, I can see the nice thing about Sage being totally self-contained and not pulling settings from a user's home directory for options. 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 -~----------~----~----~----~------~----~------~--~---
