Hi Luis! On 25 Nov., 15:43, luisfe <lftab...@yahoo.es> wrote: > I might be wrong, since coercion still looks "magic" like me. But it > seems that before trying pushout of the objects, Sage tries > L1.coerce_map_from(L2)
That's correct, and in fact this is where things go boom. > The infinite bucle looks related with caches recursion error appears > is the same as trying L1.coerce_map_from(L2). I guess that, when > trying r2_1 + r2_2 encounters the previous error but something nasty > happens with the error message... But all this needs further research. Could very well be. I tried to step through the computation using %trace. Almost immediately, the _repr_ method of number fields was called - this could very well be in order to create an error message. And then it was called over and over again. Well, let's see what debugging reveals. BTW, #8800 originally was about raising the doctest coverage of sage.categories.pushout. I found at least 10 bugs while trying to provide full doc tests coverage - and I think bugs in the coercion model are potentially very nasty, as coercion is used all over the place. Cheers, Simon -- 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
