> François,
>
> The patches to pexpect do allow the notebook to function. However, with the
> new patches to pexpect when I, from the notebook, do
>
> g=sin(x); plot(g,(x,-pi,3*pi/2))
>
> I get
>
> import os;os.chdir("/tmp/tmpo2KomY");
> execfile("_sage_input_1.py")Python 2.6.4 (r264:75706, Mar 4 2010,
> 21:15:13)
> [GCC 4.3.4] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>
> >>> import os;os.chdir("/tmp/tmpo2KomY");
> >>> execfile("_sage_input_1.py")
>
> START1
>
> import os;os.chdir("/tmp/tmpY61yjM");
> execfile("_sage_input_2.py")
>
> import os;os.chdir("/tmp/tmpXjmsQK");
> execfile("_sage_input_3.py")
> __SAGE__
> __SAGE__import os;os.chdir("/tmp/tmpY61yjM");
> __SAGE__execfile("_sage_input_2.py")
> START2
> __SAGE__
> __SAGE__import os;os.chdir("/tmp/tmpXjmsQK");
>
> The result should be the indicated graph in the notebook. So there still
> must be some functional differences between the pexpect-2.4-r1 in
> sage-on-gentoo and the pexpect-2.0_p4 provide by Sage.
Hi Steve,
Bummer. pexpect after 2.0 is a rewrite apparently. There is talk
about porting sage to a newer pexpect provided performance is
not abysmal. If it is broken, they may never want to upgrade.
Well I guess you just provided some material for discussion on sage-devel.
We may try a patched pexpect-2.0 for now, but that's a real pita.
Thanks for your testing Steve.
Francois
