On Sat, May 3, 2008 at 1:24 PM, Willem Jan Palenstijn <[EMAIL PROTECTED]> wrote: > > On Sat, May 03, 2008 at 11:57:00AM -0700, mabshoff wrote: > > On May 3, 8:44?pm, "William Stein" <[EMAIL PROTECTED]> wrote: > > > ? ? ? ? sage -t ?devel/sage/sage/rings/ring.pyx > > > know issue. Track ticket should be up shortly. Singular related. > > This is now #3098. > > It is caused by a rather subtle problem: > An expect._synchronize is being called while _another_ expect._synchronize > is still running. This caused the outer _synchronize to miss its trigger > and time-out. > > The inner one was called through the garbage collector calling > ExpectElement.__del__ calling clear() calling eval() calling > _synchronize(). > > Any ideas on how we should properly handle this? The three options I can > think of are either disabling the gc during any pexpect 'conversations' > (which doesn't seem right to me), removing the eval() from the > ExpectElement destructor (possibly using some form of delayed-evaluation > list), or finding and removing the cyclic dependency that the GC is > collecting here. I'm not entirely sure which one would be "right", if > any. > =
Another option is for clear (which is called by __del__) to simply not call _synchronize. It's really not necessary -- we just want to tell singular to kill the temp variable; it doesn't matter whether the io stream is synchronized when we do this. I tried this out and it works. I've posted a patch to trac. Please referee it. -- William --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
