[sage-devel] Re: Some polynomial timings

2017-09-06 Thread Travis Scrimshaw
> Just to correct a misconception earlier in the thread, the issue with > Skylake has nothing to do with Flint. That is an issue in MPIR which is a > community supported project. No one is currently paid to work on MPIR. > > Sorry about that; got my projects crossed. Best, Travis -- You r

Re: [sage-devel] Re: SageNB, publishing and error 500

2017-09-06 Thread Jori Mäntysalo
On Wed, 6 Sep 2017, kcrisman wrote: I suspect perhaps  https://github.com/sagemath/sagenb/commit/9dd5c0f8c783de7cb0ae21c9f445ab8260b5a0ac is the culprit, and put something on #432 to the author of that change.  It seems like the kind of thing that might happen when a module is updated, as that

Re: [sage-devel] Re: Sage 8.0 Build Error on MacOS, [mpir-3.0.0.p0] Error building MPIR.

2017-09-06 Thread 'Bill Hart' via sage-devel
That's right. For now that is the only workaround. We know what the problem is now, but don't have a working patch to fix it. It's the JMPENT macro in mpn/x86_64/x86_64-defs.m4 that doesn't work on 64 bit OSX. Details of the issue can be found here, I believe [1]. Bill. [1] https://gmplib.org/

[sage-devel] Re: Some polynomial timings

2017-09-06 Thread 'Bill Hart' via sage-devel
We are faster for sparse multivariate multiplication on multiple cores too. We just haven't blogged about it yet. :-) But you are right, Giac is years ahead at this point. We do not envision adding multivariate factorisation within the scope of the OpenDreamKit funded project that is allowing u

Re: [sage-packaging] Re: [sage-devel] Upgrade PARI to git master

2017-09-06 Thread Vincent Delecroix
On 06/09/2017 10:28, Ximin Luo wrote: Jeroen Demeyer: On 2017-09-06 14:53, Ximin Luo wrote: I've seen numerous cases where Sage has to change the expected test output simply because a dependency was upgraded. There has to be a more sustainable way of achieving this... Suggestions welcome...

Re: [sage-packaging] Re: [sage-devel] Upgrade PARI to git master

2017-09-06 Thread Ximin Luo
Jeroen Demeyer: > On 2017-09-06 14:53, Ximin Luo wrote: >> I've seen numerous cases where Sage has to change the expected test output >> simply because a dependency was upgraded. There has to be a more sustainable >> way of achieving this... > > Suggestions welcome... > > Note that none of your

Re: [sage-devel] hash issue in python3 experimental branch

2017-09-06 Thread Erik Bray
On Wed, Sep 6, 2017 at 5:13 PM, Jeroen Demeyer wrote: > On 2017-09-06 17:05, Erik Bray wrote: >> >> "language level 2" [...], where "str" means "bytes". > > > [citation needed] > > Where did you get the idea that Cython interprets "str" as "bytes" with > Python 3? > > In https://trac.sagemath.org/

[sage-devel] Re: Some polynomial timings

2017-09-06 Thread rjf
Bill Hart's blog is, as I expected, thorough and informative. It does not make for an entirely fair comparison to show timings for systems that restrict the exponents of polynomials to different lengths. That is, there are problems that can be done very simply in a system with 64 bit exponents bu

Re: [sage-devel] hash issue in python3 experimental branch

2017-09-06 Thread Erik Bray
On Wed, Sep 6, 2017 at 5:05 PM, Erik Bray wrote: > On Wed, Sep 6, 2017 at 3:35 PM, Frédéric Chapoton > wrote: >> This [b'1', b'1'] is the next problem, once the hash issue is corrected. I >> only have a branch with the added hash on my own computer at home, so I can >> not push it to trac immedi

Re: [sage-devel] hash issue in python3 experimental branch

2017-09-06 Thread Jeroen Demeyer
On 2017-09-06 17:05, Erik Bray wrote: "language level 2" [...], where "str" means "bytes". [citation needed] Where did you get the idea that Cython interprets "str" as "bytes" with Python 3? In https://trac.sagemath.org/ticket/23089 I argued *against* changing the Cython language_level.

Re: [sage-devel] hash issue in python3 experimental branch

2017-09-06 Thread Erik Bray
On Wed, Sep 6, 2017 at 3:35 PM, Frédéric Chapoton wrote: > This [b'1', b'1'] is the next problem, once the hash issue is corrected. I > only have a branch with the added hash on my own computer at home, so I can > not push it to trac immediatly. This error (and many others like it) comes from the

[sage-devel] Re: SageNB, publishing and error 500

2017-09-06 Thread kcrisman
>File > "/home/jm58660/sage/local/lib/python2.7/site-packages/sagenb/flask_version/worksheet.py", > > > line 879, in worksheet_publish > print worksheet_publish.url_for(worksheet) > >File > "/home/jm58660/sage/local/lib/python2.7/site-packages/sagenb/flask_version/worksheet.py"

Re: [sage-devel] hash issue in python3 experimental branch

2017-09-06 Thread Frédéric Chapoton
This [b'1', b'1'] is the next problem, once the hash issue is corrected. I only have a branch with the added hash on my own computer at home, so I can not push it to trac immediatly. Le mercredi 6 septembre 2017 15:29:01 UTC+2, Erik Bray a écrit : > > On Mon, Aug 28, 2017 at 8:45 PM, Frédéric C

Re: [sage-devel] hash issue in python3 experimental branch

2017-09-06 Thread Erik Bray
On Mon, Aug 28, 2017 at 8:45 PM, Frédéric Chapoton wrote: > Indeed, adding __hash__ to the CDF class seems to fix this specific issue. I > wonder how many hash we are going to be forced to add.. I've finally gotten my python3 build to a point where I'm able to reproduce this problem. Have you co

Re: [sage-devel] Upgrade PARI to git master

2017-09-06 Thread John Cremona
On 6 September 2017 at 12:48, Jeroen Demeyer wrote: > On 2017-07-25 22:16, Jeroen Demeyer wrote: >> >> Hello sage-devel and sage-packaging, >> >> I propose to upgrade the PARI package to the git master version instead >> of the current released version. > > > Now that the cypari2 upgrade has been

Re: [sage-devel] Upgrade PARI to git master

2017-09-06 Thread Jeroen Demeyer
On 2017-07-25 22:16, Jeroen Demeyer wrote: Hello sage-devel and sage-packaging, I propose to upgrade the PARI package to the git master version instead of the current released version. Now that the cypari2 upgrade has been merged, I am working on this. Thanks to the new cypari2, *building* Sa

[sage-devel] SAGE_PATH and PYTHONPATH

2017-09-06 Thread Ralf Hemmecke
Since my settings using SAGE_PATH do seemingly not work anymore, I looked for the use of SAGE_PATH in the sources. I found in 7.6 some code if [ -n "$SAGE_PATH" ]; then PYTHONPATH="$SAGE_PATH:$PYTHONPATH" fi but that was removed in commit 22e470c2d6941875908f35ff3657843f1fe83f21