2009/9/6 William Stein <[email protected]>: > > 2009/9/5 Paulo César Pereira de Andrade > <[email protected]>: >> >> 2009/9/5 William Stein <[email protected]>: >>> >>> 2009/9/5 Paulo César Pereira de Andrade >>> <[email protected]>: >>>> >>>> Hi, >>>> >>>> I am not experienced with pexepect, but I played a bit trying to use >>>> a newer version in sage. >>>> But since it is one of the core packages of sage (and because it is >>>> one of the special cases where an older package is used, in my rpm >>>> package :-), I would like to know what is the state about upgrading it >>>> to a newer version, or using some alternate interface. >>> >>> The only reason I didn't upgrade pexpect long ago is that at some >>> point it was greatly rewritten/refactored and the result was >>> *massively* slower than the version in Sage. So I stayed with the >>> version we were including. Nobody has succeeded in figuring out why >>> the new pexpect is thousands of times slower. >>> >>>> >>>> The major problems I see are: >>> >>> Major problems with upgrading? Or with pexpect in general? >>> >>>> 1. pexpect uses a pty, but it is not a fully functional "terminal >>>> emulator", for example, try any gap command longer then 80 bytes; it >>>> will get completely wrong. >>> >>> That is not true at all. >>> >>> sage: a = '2'*90 >>> sage: gap.eval('%s + 1'%a) >>> '222222222222222222222222222222222222222222222222222222222222222222222222222222222222222223' >>> >>> That's a 90 character command and it is not "completely wrong". >> >> Oops, I think I extended one behavior as if it were generalized, >> should have confused with some test with newer pexpect, sorry. But one >> way to reproduce the problem can be to do something like: >> >> % mkdir -p >> /tmp/0123456789/0123456789/0123456789/0123456789/0123456789/0123456789/0123456789/.sage >> <<make sure DOT_SAGE will point to that directory>> >> % sage >> <<exit sage>> >> % ls >> /tmp/0123456789/0123456789/0123456789/0123456789/0123456789/0123456789/0123456789/.sage/gap/ >> README.txt >> <<change DOT_SAGE to something like just /tmp/0123456789/>> >> % sage >> <<exit sage>> >> % ls /tmp/0123456789/.sage/gap >> README.txt workspace-1328071335 >> >> This happens because the SaveWorkspace() call had more then 80 characters, >> and it severely bugs out when trying to build the documentation, because I >> would >> set DOT_SAGE to the rpm buildroot, but now it uses a hack to >> export DOT_SAGE=/tmp/sage$$ > > Can you please please post this stuff to trac.sagemath.org? I won't > be able to work on sage development for the next few weeks, and I > don't want this to get lost in the shuffle.
No problems. I just need a trac account. I think you may have missed my request because I used the same subject for a post to sage-devel and one private mail :-) I can later try to also provide a patch to use latest upstream pexpect, I had one, but was somewhat trivial, just that it would only work correctly in the sage terminal interface, while frequently displaying a lot of noise in the notebook, usually when loading maxima, singular, or other background process, what should have been a timing issue. [ to avoid one possible round trip, my preferred account name would be pcpa, and I had suggest as the password the google mail identifier of that private email ] > William Thanks, Paulo --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
