>> (1) gcd is broken. http://trac.sagemath.org/sage_trac/ticket/10459
[..]
> I'm personally OK either way with this.
IMO a*b = gcd(a,b)*lcm(a,b) should be maintained wherever possible.
There are pari codes whose direct Sage equivalent silently breaks for
this reason, and I can't bring myself to admit it to my pari-speaking
friends. :^)
> Could you post an example [re: my whitespace issues --ed] to nail down
> exactly what you're talking about?
sage: s = 'for i in range(3):\n' + ' '*4 + 'print i\n'
sage: # add extra space, such as can often happen in practice
sage: # when writing code, and I can't see it, because, well,
sage: # it's whitespace..
sage: s = s + '\n' + ' '*4 + '\n'
sage:
sage: fname = 'whitespace_pedantic.sage'
sage: with open(fname,'w') as fp:
....: fp.write(s)
....:
sage: # Python is happy
sage: execfile(fname)
0
1
2
sage: # Sage is not
sage: load(fname)
------------------------------------------------------------
File "<string>", line 5
^
SyntaxError: invalid syntax
Doug
--
Department of Earth Sciences
University of Hong Kong
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
