On Monday, September 9, 2019 at 2:06:21 PM UTC-7, Jeroen Demeyer wrote: > > On Mon, Sep 9, 2019 at 7:51 PM John H Palmieri <jhpalm...@gmail.com > <javascript:>> wrote: > > I am writing to ask for help fixing a Python 3 problem. On some > platforms, there are Python 3 doctest failures in > > > > - libs/eclib/interface.py (#28454) > > I believe that this has been fixed upstream, it has certainly been > reported by me. Are we using the latest eclib version? > > > How do we fix this? Note that patching FLINT is not ideal, since it > won't help users who are using the system's version of the library. FLINT's > most recent release was in 2015, so I don't know how much we can expect > from upstream regarding new releases. So maybe the ideal solution would be > to get Python to flush the output from these external libraries. I don't > know how to do this; can anyone else help? > > Ideally, the upstream library should properly flush when producing > output. They should use fflush (in C) or std::endl or std::flush (in > C++). I guess that Sage could also do the flushing whenever we return > from a library API call. >
This problem arises with polynomial_rational_flint.pyx (on Ubuntu and Debian but not OS X, for whatever reason). See https://trac.sagemath.org/ticket/28334. How can we do this flushing? The only other solution I can see is to patch FLINT, but this won't work if users are using a system-wide installation of FLINT. Other flushing problems appear at #28454, now since fixed with an upgrade to eclib, and #28622: pure Python code, so adding some `sys.stdout.flush()` commands cleared up that problem. But the FLINT problem remains. -- John -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/bc6e7a4a-c8a3-4511-94ec-718e0126b19e%40googlegroups.com.
