On 05/08/15 14:08, Bill Page wrote:
On 7 May 2015 at 21:37, François Bissey
<francois.bis...@canterbury.ac.nz> wrote:
Looks like I would want this single commit.
https://github.com/pexpect/pexpect/commit/aac5897aa12daf056b8fe08f1b6512d9f60c2d27
The branch seems otherwise strangely stale (210 commits
behind master).

Yes. I suppose that branch 3.x is (more or less) release 3.4  But
there is already announced a version 4.0

https://github.com/pexpect/pexpect/blob/master/doc/history.rst

But there is no branch specific to 4.x.  I suppose that is in fact the
master branch.  Although they use the word "release" it is not obvious
to me where to find the source or installable for a specific release.

I have not tried "4.0" yet but if it is "released" and a significant
number of fixes ahead of "3.4" then perhaps we should try to skip
right to it?

Well the fix we are interested in *is not* in master. But would be trivial to add. I am looking at the notebook and it doesn't look pretty
but I am trying to make sure there are no external influences before
confirming whether it is broken or not.

Other than that the only doctest failing from a file import pexpect is
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 1022, in sage.interfaces.expect.Expect._expect_expr
Failed example:
    r._expect.before
Expected:
    'abc;\r\n[1] '
Got:
    'abc <- 10 +15;\r\n__SAGE__R__PROMPT__> abc;\r\n[1] '
**********************************************************************
which is a bit strange.

Francois

--
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.

Reply via email to