If you want doctests failures here is a sample (6.7.beta4):
sage -t --long
/usr/lib64/python2.7/site-packages/sage/interfaces/expect.py
**********************************************************************
File "/usr/lib64/python2.7/site-packages/sage/interfaces/expect.py",
line 285, in sage.interfaces.expect.Expect.pid
Failed example:
pid = gap.pid()
Exception raised:
Traceback (most recent call last):
File
"/usr/lib64/python2.7/site-packages/sage/doctest/forker.py", line
496, in _run
self.compile_and_execute(example, compiler, test.globs)
File
"/usr/lib64/python2.7/site-packages/sage/doctest/forker.py", line
858, in compile_and_execute
exec(compiled, globs)
File "<doctest sage.interfaces.expect.Expect.pid[0]>", line 1,
in <module>
pid = gap.pid()
File
"/usr/lib64/python2.7/site-packages/sage/interfaces/expect.py", line
296, in pid
self._start()
File
"/usr/lib64/python2.7/site-packages/sage/interfaces/gap.py", line
1168, in _start
gap_reset_workspace(verbose=False)
File
"/usr/lib64/python2.7/site-packages/sage/interfaces/gap.py", line
1507, in gap_reset_workspace
g.eval('SetUserPreference("HistoryMaxLines", 30)')
File
"/usr/lib64/python2.7/site-packages/sage/interfaces/gap.py", line
570, in eval
result = Expect.eval(self, input_line, **kwds)
File
"/usr/lib64/python2.7/site-packages/sage/interfaces/expect.py", line
1222, in eval
for L in code.split('\n') if L != ''])
File
"/usr/lib64/python2.7/site-packages/sage/interfaces/gap.py", line
727, in _eval_line
self._start()
File
"/usr/lib64/python2.7/site-packages/sage/interfaces/gap.py", line
1163, in _start
Expect._start(self, "Failed to start GAP.")
File
"/usr/lib64/python2.7/site-packages/sage/interfaces/expect.py", line
425, in _start
self._expect = pexpect.spawn(cmd, logfile=self.__logfile,
env=pexpect_env)
File "/usr/lib64/python2.7/site-packages/pexpect/__init__.py",
line 493, in __init__
fd = sys.__stdin__.fileno()
ValueError: I/O operation on closed file
this particular failure is all over the place with pexpect 3.3 so
there is
something that is in need of updating on expect.py side before going
ahead.
François
On 7/05/2015, at 14:59, Bill Page <bill.p...@newsynthesis.org> wrote:
Is there a possibility of creating an experimental package to install
pexpect 3.3 ?
I see references to "doctests failing" but no details. It would be
good to make this easier to test.
On 6 May 2015 at 22:41, leif <not.rea...@online.de> wrote:
Bill Page wrote:
After reading the docs:
http://pexpect.readthedocs.org/en/latest/index.html
It seems that version 3 and later are supposed to handler unicode
properly. Version 3.3 requires Python 2.6 or later. Since Sage is
already at Python 2.7 is there a good reason why Sage is still using
an older version of pexpect?
http://trac.sagemath.org/ticket/502 (!)
http://trac.sagemath.org/ticket/10295
--
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/d/optout.
--
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/d/optout.
