From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo] sage-notebook fix is in
Date: Sat, 13 Mar 2010 23:17:18 -0600 [thread overview]
Message-ID: <1268543846.20285.0@pavilion64> (raw)
In-Reply-To: <201003141059.03540.f.r.bissey@massey.ac.nz> (from f.r.bissey@massey.ac.nz on Sat Mar 13 15:59:03 2010)
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
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.
Steve
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-14 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 21:59 [gentoo-science] [sage-on-gentoo] sage-notebook fix is in François Bissey
2010-03-14 5:17 ` Steven Trogdon [this message]
2010-03-14 6:27 ` François Bissey
2010-03-14 7:46 ` Christopher Schwan
2010-03-14 7:53 ` François Bissey
2010-03-14 8:01 ` François Bissey
2010-03-14 7:57 ` Christopher Schwan
2010-03-14 11:17 ` Steven Trogdon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1268543846.20285.0@pavilion64 \
--to=strogdon@d.umn.edu \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox