Hi, On 24 Okt., 01:00, Willem Jan Palenstijn <[EMAIL PROTECTED]> wrote: > On Thu, Oct 23, 2008 at 02:20:42PM -0700, Georg S. Weber wrote: > > 3. Even the innocent line > > > sage: time for i in range(10): float(1)/2 > > This seems to be caused by the _record_exception() function in the > coercion model. Specifically, the function canonical_coercion() in > coerce.pyx calls this after casting the float to Integer fails. > > Example that should trigger it: > > sage: cm = sage.structure.element.get_coercion_model() > sage: cm.canonical_coercion(float(1),1)
Yeah, this example triggers the behaviour, too. And since Sage 3.0.5 does not show that search sys.path issue (tested with the "sage: time for i in range(10): float(1)/2" example), I just opened trac ticket #4366 about it with "component: coercion". Thanks for all the helpful tips (I really didn't think about e.g. the ? and ?? feature)! Cheers, gsw > > -Willem Jan --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
