On Fri, Feb 5, 2010 at 8:12 AM, John Cremona <john.crem...@gmail.com> wrote: > Here's the explanation. I had thought that check=False just stops the > check that the equations are satisfied (I posted an examples where > there were no equations which perhaps hid my point; I found this > while constructing points on a curve in P^2). But in fact it checks > nothing at all. > > All I would want to do is change the line self._coords = v to > self._coords = list(v) at the appropriate place. If that failed, then > it's the user's false. In this case it did not fail and almost > everything worked, except that I got inconsistencies in sorting points > since the sort function tearted a point with _coords as list > differently from points with _coords as tuple!
But the reason for check=False is that it is useful for writing internal code, where you want to avoid the potentially substantial overhead of operations such as "list(v)". Maybe we need another option? E.g., check_ring or something? -- William -- 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
