Hello everybody,
During Sage Days 66, Erik Rowland gave us an overview of what working
with Mathematica looks like.
He showed us that one can consider the square root of a picture of a
siamese cat, but also a nice feature: one can very easily display a
list of objects, some of which are
He showed us that one can consider the square root of a picture of a
siamese cat, but also a nice feature: one can very easily display a
list of objects, some of which are decorated with a frame or a
background color. This is very useful, I believe, when one looks at a
Are you
On Saturday, 31 January 2015 16:22:09 UTC-5, Dr. David Kirkby (Kirkby
Microwave Ltd) wrote:
On 22 December 2014 at 00:43, Robert Jacobson rljac...@gmail.com
javascript: wrote:
Hi. I have yet to contribute code to sage, but I think I've found
something
easy enough for me to start with.
On 2015-04-05 09:44, Simon King wrote:
Seriously? Since when? I always get errors when I forget to cdefine
something that will end up as something that is not of a Python type.
Random example where this is used in Sage: look at
structure/coerce_dict.pyx
cdef int MonoDict_traverse(MonoDict op,
$ git fetch trac e070dd191bb189b83bae5a2a5c12bf4d70981040
From trac.sagemath.org:sage
* branche070dd191bb189b83bae5a2a5c12bf4d70981040 - FETCH_HEAD
$ echo $?
0
Interesting, I get return code 0. Did it actually fetch anything (ie.
FETCH_HEAD is set)? Why didn't it print anything to
I took a not-so clean Sage-6.5 install, installed git-trac (with no
keys or login/password) and tried to check out the code from ticket
17826 (upgrade Ipython). I just get some mysterious errors.How am
I supposed to debug this?
salvus@devel1dc5:/usr/local/sage/current$ git trac checkout
Hi,
Please consider this question low priority -- I can just directly make
the changes to upgrade sage-6.5 to IPython 3 for now, then wait for
sage-6.6, which should appear any minute now anyways.
That said, shouldn't git fetch trac actually display some sort of
error rather than just exiting
