1 | initial version |
Fortunately (?), this is a general sage problem (nothing to do with sagemathcloud). It's caused by the sage pre-parser making the 0 a Sage integer. Either use %python or int(0) or 0r to workaround it:
https://cloud.sagemath.com/projects/4a5f0542-5873-4eed-a85c-a18c706e8bcd/files/support/2015-02-17-080429-ask.sagews