> 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).
It is important to
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 a
> 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
William Stein wrote:
>
> 4. Do export MPLCONFIGDIR=$DOT_SAGE/matplotlibconfig
>
> That avoids every single problem above. :-)
Brilliant. It does leave an unused and possibly confusing matplotlibrc
file in their .sage directory, but I suppose that's happening right now,
so it's not any worse
2009/6/6 Jason Grout :
>
> 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
>>
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 dire
>> 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.
>
> Yep, it does. We can make sure easily enough by running Sage and asking:
>
> sage: DOT_SAGE
> '/Users/wstein/.sage/'
>
> By the way, I j
2009/6/6 Brian Granger :
>
>> 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
> 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 i
On Tue, May 19, 2009 at 12:18 PM, Brian Granger wrote:
>
>> 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.
>
> The problem that I am running into is that my
> ~./matplotlib/matplotlibrc s
> 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.
The problem that I am running into is that my
~./matplotlib/matplotlibrc sets a backend (macosx) that the Sage
matplotlib doesn't have. Th
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 lon
> 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 matplotli
OK
On Mon, May 18, 2009 at 3:31 PM, Michael Abshoff
wrote:
>
> Hi Brian,
>
> no need to CC me on bug reports you send to sage-devel.
>
> Cheers,
>
> Michael
>
> >
>
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscr
Hi Brian,
no need to CC me on bug reports you send to sage-devel.
Cheers,
Michael
--~--~-~--~~~---~--~~
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 mo
Brian Granger wrote:
> True, we fixed this in SPD because it is a problem there, however, I
> also have this problem with Sage. I download Sage, install it, and it
> doesn't work (because I have a .matplotlib/matplotlibrc file).
>
> I will look around for previous posts on this though.
>
Detai
True, we fixed this in SPD because it is a problem there, however, I
also have this problem with Sage. I download Sage, install it, and it
doesn't work (because I have a .matplotlib/matplotlibrc file).
I will look around for previous posts on this though.
Brian
On Mon, May 18, 2009 at 2:58 PM,
On Mon, May 18, 2009 at 2:51 PM, Brian Granger wrote:
>
> Currently:
>
> IF a user has matplotlib installed outside of Sage
> AND they have a matplotlibrc file in ~/.matplotlib
>
> THEN Sage will use the non-Sage version in ~/.matplotlib/matplotlibrc.
> If a user has set a frontend (such as WxAg
18 matches
Mail list logo
