This is similar to http://trac.sagemath.org/15440, the problem boils down to: The expect pattern must(!) trigger at a place where all input has been eaten. Including newline/spaces. If not then there is still input coming into the subprocess, and the echo of that further input will show up at random places in the output stream.
The annoying thing is that it is hard to test that the expect is being used correctly, and that it leads to somewhat improbable Heisenbugs. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
