[sage-devel] sagemath 8.3 rc0

2018-07-09 Thread aishen
Hi, I couldn't compile previous version, always some errors. But this rc0 passed without any problems ! ubuntu xenial AMD 64 8 x 16 Go RAM. Regards Henri -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop r

Re: [sage-devel] Re: How parallel should @parallel be?

2018-07-09 Thread Nils Bruin
On Monday, July 9, 2018 at 9:49:12 PM UTC-7, Jori Mäntysalo wrote: > > On Mon, 9 Jul 2018, John H Palmieri wrote: > > >> I would also expect it to run as many threads as my laptop has > >> cores (+ hyperthreading if available). > > > This makes sense for single-user machines, but the current def

Re: [sage-devel] Re: How parallel should @parallel be?

2018-07-09 Thread Jori Mäntysalo
On Mon, 9 Jul 2018, John H Palmieri wrote: I would also expect it to run as many threads as my laptop has cores (+ hyperthreading if available). This makes sense for single-user machines, but the current default was implemented because it was deemed safer on machines used by multiple users.

[sage-devel] Re: How parallel should @parallel be?

2018-07-09 Thread John H Palmieri
On Monday, July 9, 2018 at 2:27:20 PM UTC-7, Friedrich Wiemer wrote: > > I would also expect it to run as many threads as my laptop has cores (+ > hyperthreading if available). > This makes sense for single-user machines, but the current default was implemented because it was deemed safer on m

[sage-devel] Re: How parallel should @parallel be?

2018-07-09 Thread Sébastien Labbé
> > The question is: What is a good default for things such as @parallel when > SAGE_NUM_THREADS has not been set? I think that 1 is not a good one. > +1 The actual number of cores/threads on a system probably isn't either on > servers with lots of cores. At some point we had `min(8, number

[sage-devel] Re: How parallel should @parallel be?

2018-07-09 Thread Friedrich Wiemer
I would also expect it to run as many threads as my laptop has cores (+ hyperthreading if available). -- 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+u

[sage-devel] Re: Sage fails to build on Arch linux, possible recurrence of an old bug

2018-07-09 Thread Amit Wolecki
Thank you all for the useful comments! Antonio, I wasn't aware of the somewhat limiting way a repo installation works, this remark made me try to stick to building from source. Thanks Timo for the emphasis, compiling the develop branch was smooth, I'd switch back to 8.2+patch if needed. Cheers, A

Re: [sage-devel] How parallel should @parallel be?

2018-07-09 Thread Jori Mäntysalo
On Mon, 9 Jul 2018, Julian Rüth wrote: The question is: What is a good default for things such as @parallel when SAGE_NUM_THREADS has not been set? I think that 1 is not a good one. The actual number of cores/threads on a system probably isn't either on servers with lots of cores. At some point

[sage-devel] How parallel should @parallel be?

2018-07-09 Thread Julian Rüth
Hello. since Sage 8.2 sage.parallel.ncpus.ncpus() returns 1 if you have no environment variables such as MAKE, SAGE_NUM_THREADS, MAKEOPTS set. This number is used by the @parallel decorator and similar constructions to determine the number of processes to run in parallel. (Unless during docte

[sage-devel] Re: NTL 11.2.0

2018-07-09 Thread 'Bill Hart' via sage-devel
These are ery interesting timings. In the region above the diagonal (and sufficiently far to the right - degree 12 I think), I believe we still use the SSA algorithm directly for polynomial arithmetic over Z. So your timings indicate that you are actually beating the Flint FFT directly. This is

Re: [sage-devel] Matplotlib plotting style 'classic' hardcoded to Sage

2018-07-09 Thread Kwankyu Lee
Consulting https://matplotlib.org/users/dflt_style_changes.html we may keep specifically only the math font of the classic style by: mpl.rcParams['mathtext.fontset'] = 'cm' mpl.rcParams['mathtext.rm'] = 'serif' and adopt the default matplotlib-2 style generally. I assume that the matplotlib-2

Re: [sage-devel] Re: Trac branch trouble?

2018-07-09 Thread Erik Bray
On Mon, Jul 9, 2018 at 8:33 AM Simon King wrote: > > On 2018-07-08, Volker Braun wrote: > > The commit SHA1 is immutable, but the branch can evolve over time. > > There is a "commit" field on trac, as you know. So, why is there a > pressing need to replace the "branch" field by the content of the

Re: [sage-devel] Matplotlib plotting style 'classic' hardcoded to Sage

2018-07-09 Thread François Bissey
Generally equations look better with the font choices in the “classic” style which was the default before matplotlib-2. > On 9/07/2018, at 20:34, Kwankyu Lee wrote: > > Yeah, I found one thing that looks ugly on my machine: > > In the 'classic' style: > > > In the current default style: >

Re: [sage-devel] Matplotlib plotting style 'classic' hardcoded to Sage

2018-07-09 Thread Kwankyu Lee
Yeah, I found one thing that looks ugly on my machine: In the 'classic' style: In the current default style: -- 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

Re: [sage-devel] Matplotlib plotting style 'classic' hardcoded to Sage

2018-07-09 Thread Kwankyu Lee
On Monday, July 9, 2018 at 10:40:03 AM UTC+9, François Bissey wrote: > > I am sorry to have introduced that in the upgrade to matplotlib 2.1. > Hardcoding > was easier than setting the style to classic for every calls for the > documentation. > The reports I had was that the default style fro