Thank you for the patch Mike, It works great.
And, thank you for the recommendation on Python books, William.
On Jun 15, 3:04 pm, Mike Hansen wrote:
> On Mon, Jun 15, 2009 at 9:59 AM, William Stein wrote:
> >>> It's completely broken. This is a new bug in Sage-4.0, which was
> >>> introduced b
On Mon, Jun 15, 2009 at 9:59 AM, William Stein wrote:
>>> It's completely broken. This is a new bug in Sage-4.0, which was
>>> introduced by factoring dsage out from the core sage library, I think
>>> by Mike Hansen. I've opened a blocker ticket for this:
>>>
>>> http://trac.sagemath.org/sage_tr
On Mon, Jun 15, 2009 at 6:48 PM, lenient7 wrote:
>
> Thank you William,
>
> I am seriously considering learning Python. In any case, it looks like
> that I need to be versatile with Python to use Sage well.
Check out this awesome free book:
http://www.diveintopython.org/
My favorite non-free Py
Thank you William,
I am seriously considering learning Python. In any case, it looks like
that I need to be versatile with Python to use Sage well.
On Jun 15, 11:39 am, William Stein wrote:
> On Mon, Jun 15, 2009 at 5:03 PM, lenient7 wrote:
>
> > Hello everyone,
>
> > I am very new to the sage.
On Mon, Jun 15, 2009 at 5:03 PM, lenient7 wrote:
>
> Hello everyone,
>
> I am very new to the sage.
>
> I tried to use the sage from a remote client. On that regard, I am
> running the Sage 4.0.1 on OpenSUSE 11.1 64bit edition. However when I
> am trying to run notebook with 'secure=True' option,