Re: [sage-devel] Python 3 and flushing output from external libraries

On Wednesday, October 23, 2019 at 2:47:54 PM UTC-7, John H Palmieri wrote: > > > > On Wednesday, October 23, 2019 at 1:41:35 PM UTC-7, Nils Bruin wrote: >> >> On Wednesday, October 23, 2019 at 1:26:46 PM UTC-7, John Cremona wrote: >>> >>> >>> That all looks very complicated. Before I fixed the

Re: [sage-devel] Python 3 and flushing output from external libraries

On Wednesday, October 23, 2019 at 1:41:35 PM UTC-7, Nils Bruin wrote: > > On Wednesday, October 23, 2019 at 1:26:46 PM UTC-7, John Cremona wrote: >> >> >> That all looks very complicated. Before I fixed the eclib source code >> the previous method did work, namely to flush stdout and stderr

[sage-devel] Re: Gram-Schmidt Procedure for Symbolic Ring

Well... the error message is pretty explicit: since sage: SR.is_exact() False M.gram_schmidt() wont work if M.base_ring is SR. Creating a second special case for SR may not be as simple as for RDF, since a lot of other cases (beyond RDF) can happen in this case Le mardi 22 octobre 2019

Re: [sage-devel] Python 3 and flushing output from external libraries

On Wednesday, October 23, 2019 at 1:26:46 PM UTC-7, John Cremona wrote: > > > That all looks very complicated. Before I fixed the eclib source code the > previous method did work, namely to flush stdout and stderr from the > c/python wrapper code after calling any library function (in some

[sage-devel] Re: sage and emacs (and unicode)

BTW, the original creator of sage-shell-mode (someone calling himself "skatemori" on Github) seems to have dropped out of github at the end of Winter 2018. As a corollary, another of ios Sage-related projects ob-sagemath , is no longer maintained.

Re: [sage-devel] Python 3 and flushing output from external libraries

On Wed, 23 Oct 2019 at 21:12, John H Palmieri wrote: > I found that and > https://stackoverflow.com/questions/5081657/how-do-i-prevent-a-c-shared-library-to-print-on-stdout-in-python > and maybe other related items, but I couldn't figure out how to use them to > fix this particular problem.

[sage-devel] Re: sage and emacs (and unicode)

The problem is a tad larger, as illustrated in this age-shell-mode issue ... It probably is a small patch to do (an oversight of strr<--> unicode conversion, revealed by our switch to Python3...) Le mardi 22 octobre 2019 12:22:43 UTC+2,

Re: [sage-devel] Python 3 and flushing output from external libraries

I found that and https://stackoverflow.com/questions/5081657/how-do-i-prevent-a-c-shared-library-to-print-on-stdout-in-python and maybe other related items, but I couldn't figure out how to use them to fix this particular problem. Others will know what they're doing more than I do regarding a

Re: [sage-devel] Python 3 and flushing output from external libraries

an internet search finds https://stackoverflow.com/questions/4178614/suppressing-output-of-module-calling-outside-library is it what would work for us? On Wed, 23 Oct 2019, 20:06 John H Palmieri, wrote: > > > On Monday, September 9, 2019 at 2:06:21 PM UTC-7, Jeroen Demeyer wrote: >> >> On Mon,

Re: [sage-devel] Python 3 and flushing output from external libraries

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

[sage-devel] Re: sage.plot.graphics.GraphicsArray no longer available?

Sorry for jumping the gun. The improved version is sage.plot.multigraphics.GraphicsArray(array) http://doc.sagemath.org/html/en/reference/plotting/sage/plot/multigraphics.html#module-sage.plot.multigraphics On Wednesday, October 23, 2019 at 10:24:08 AM UTC-7, Pong wrote: > > I have updated to

[sage-devel] sage.plot.graphics.GraphicsArray no longer available?

I have updated to the latest sage (from the cocalc git) last night and have just found out that the module sage.plot.graphics.GraphicsArray is no longer available. Is that true? If so, what would be a replacement for that? -- You received this message because you are subscribed to the Google

Re: [sage-devel] Compile sage with `-march=native` as a default

Thanks for your replies. I wasn't aware of `CFLAGS` and it works great. I think it makes sense to enable the SIMD-instructions with #27103 no matter if all of sage is compiled with `-march=native` by default. All it really takes to get the intrinsics