[sage-devel] flushing stdout during doctests

2019-02-26 Thread John Cremona
I am testing a new version of the standard spkg eclib, see https://trac.sagemath.org/ticket/27360. I am getting doctesting failures caused *only* because of changes in output buffering resulting in the tail end of the output of one command appearing at the beginning of the output of the next. For

Re: [sage-devel] flushing stdout during doctests

2019-02-27 Thread Jeroen Demeyer
On 2019-02-26 17:52, John Cremona wrote: I am testing a new version of the standard spkg eclib, see https://trac.sagemath.org/ticket/27360. I am getting doctesting failures caused *only* because of changes in output buffering resulting in the tail end of the output of one command appearing at th

Re: [sage-devel] flushing stdout during doctests

2019-02-27 Thread John Cremona
On Wed, 27 Feb 2019 at 08:56, Jeroen Demeyer wrote: > On 2019-02-26 17:52, John Cremona wrote: > > I am testing a new version of the standard spkg eclib, see > > https://trac.sagemath.org/ticket/27360. I am getting doctesting > > failures caused *only* because of changes in output buffering resu

Re: [sage-devel] flushing stdout during doctests

2019-02-27 Thread Jeroen Demeyer
On 2019-02-26 17:52, John Cremona wrote: I am testing a new version of the standard spkg eclib, see https://trac.sagemath.org/ticket/27360. I am getting doctesting failures caused *only* because of changes in output buffering resulting in the tail end of the output of one command appearing at th

Re: [sage-devel] flushing stdout during doctests

2019-02-27 Thread John Cremona
On Wed, 27 Feb 2019 at 09:16, Jeroen Demeyer wrote: > On 2019-02-26 17:52, John Cremona wrote: > > I am testing a new version of the standard spkg eclib, see > > https://trac.sagemath.org/ticket/27360. I am getting doctesting > > failures caused *only* because of changes in output buffering resu