Now I'm confused, it looks like the patch in 2339 was applied but it
doesn't fix the problem like it used to.
-M. Hampton
On Aug 24, 10:40 am, mhampton <[EMAIL PROTECTED]> wrote:
> I thought J. Palmieri and I had fixed that, but it looks like his
> patch hasn't made it in for some reason. It is
I thought J. Palmieri and I had fixed that, but it looks like his
patch hasn't made it in for some reason. It is trac 2339:
http://trac.sagemath.org/sage_trac/ticket/2339
That said, I think the way Sage uses matplotlib currently is somewhat
confusing and 2D plotting needs lots of other work (on
On Sat, Aug 23, 2008 at 11:58 AM, Philippe Saade <[EMAIL PROTECTED]> wrote:
>
> On Sat, Aug 23, 2008 at 7:47 PM, Arnaud Bergeron <[EMAIL PROTECTED]> wrote:
>>
>> 2008/8/23 Philippe Saade <[EMAIL PROTECTED]>:
>>>
>>> Hi group,
>>>
>>> i'am a little bit confused while analysing Sage Python packages
On Sat, Aug 23, 2008 at 7:47 PM, Arnaud Bergeron <[EMAIL PROTECTED]> wrote:
>
> 2008/8/23 Philippe Saade <[EMAIL PROTECTED]>:
>>
>> Hi group,
>>
>> i'am a little bit confused while analysing Sage Python packages and
>> (newbie's default) a would like to ask a simple question :
>
> For the next tim
2008/8/23 Philippe Saade <[EMAIL PROTECTED]>:
>
> Hi group,
>
> i'am a little bit confused while analysing Sage Python packages and
> (newbie's default) a would like to ask a simple question :
For the next time, this sort of question goes to [EMAIL PROTECTED]
> when one types
>
> var('x')
> f_ex
