Hey Harald (et al)-
I am wondering if this is a general bug in the sage notebook - I seem
to be having this problem with sage-4.7.alpha2 (not running the flask
notebook, just the usual one). Can someone else try this to confirm?
-Marshall
On Mar 27, 4:56 am, Harald Schilly wrote:
> On Saturday
On 3/28/11 9:16 PM, mhampton wrote:
Presumably this is the blog of the author:
http://www.shocksolution.com
If so, his background is more in scientific computing than most Sage
developers, and it seems like a good thing to have a book out that
might appeal to that audience.
Here's a particular
Presumably this is the blog of the author:
http://www.shocksolution.com
If so, his background is more in scientific computing than most Sage
developers, and it seems like a good thing to have a book out that
might appeal to that audience.
--
To post to this group, send an email to sage-devel@goo
On Mar 28, 2011, at 17:21 , Dr. David Kirkby wrote:
> I know a few people (myself included) were asked to write a book on Sage.
> Anyway, someone by the name of Craig Finch has. The book should be available
> May of this year.
>
> https://www.packtpub.com/sage-beginners-guide/book
Love the ta
I know a few people (myself included) were asked to write a book on Sage.
Anyway, someone by the name of Craig Finch has. The book should be available May
of this year.
https://www.packtpub.com/sage-beginners-guide/book
ISBN : 1849514461
ISBN 13 : 978-1-84951-446-0
It will be available on Ama
Dear Poset fans,
My patch is now under "needs review":
http://trac.sagemath.org/sage_trac/ticket/10998
So that's a call for volunteers for reviewing it. Christian, Frédéric,
are you still up for that? What's your time line?
Cheers,
Nicolas
--
Nicolas M. T
On 3/27/11 10:28 AM, Mike Hansen wrote:
Hello,
On Sun, Mar 27, 2011 at 1:08 AM, Jason Grout
wrote:
Rado or Mike: how do you think we should get jmol requests to be recognized
as requests coming from an authenticated user?
The issue is that the secure cookie that Flask uses is sent as
httpon
This is a reminder on how to properly submit a patch to Trac.
Recently, I find a lot of small administrative issues. Please keep in
mind the following:
1) When submitting a patch, make sure there is reasonable *commit
message* (use hg qrefresh -e to set the message). The message is
allowed to sp
