[sage-devel] Re: NTL v10

On Tuesday, October 11, 2016 at 6:06:50 AM UTC+2, Victor Shoup wrote: > > I looked at the singular patch, regarding the use of nothrow new. > I dug up "ticket #852" which lead to that patch. > In all honesty, it looks like singular is doing something wrong, > so "fixing" NTL is just the wrong thi

Re: [sage-devel] NTL v10

Hum sorry I did not read the previous posts completely. -- 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 post to this g

Re: [sage-devel] NTL v10

Using MAKE also let you trigger parallel build for subtargets with MAKE="make -j128". Given the current use of make within the makefile it is not really the case. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

Re: [sage-devel] NTL v10

On Monday, October 10, 2016 at 3:53:34 PM UTC+2, Victor Shoup wrote: > > Let me get this straight... > You say that the tarball does not contain a libtool script, but rather, > contains a directory that contains files that will build a libtool script > at compile time. Is that right? Which tar

Re: [sage-devel] NTL v10

On Monday, October 10, 2016 at 2:58:38 PM UTC+2, Victor Shoup wrote: > > Ok, I will start working on these issues. The one I understand the least > is libtool. > It looks like you are saying I should generate a libtool script on the > machine X on which > I create the NTL tarball. But this see

Re: [sage-devel] NTL v10

Thanks for the hint, we are already a few versions behind. I've opened #21676 for us to update, if anyone wants to review it: * https://trac.sagemath.org/ticket/21676#ticket By the way we are still shipping a few patches, have a look at: * https://github.com/sagemath/sage/blob/master/build/pkgs/n

Re: [sage-devel] multithreading performance issues

>> we have decided to let fflas-ffpack the possibility to force the number of >> threads that OpenBLAS can use at runtime. In this context we will force it >> to 1. >> This is available upsteam and I plan to update sage's fflas-ffpack >> whenever we release v2.3

Re: [sage-devel] multithreading performance issues

Currently OpenBlas does what it wants for multithreading. We hesitated to disable it but prefered to wait and think about it: see https://trac.sagemath.org/ticket/21323. You can still influence its use of threads setting OPENBLAS_NUM_THREADS. See the trac ticket, just note that this is not Sage sp

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

On Monday, October 3, 2016 at 4:04:20 PM UTC+2, Dima Pasechnik wrote: > > > > On Monday, October 3, 2016 at 11:48:22 AM UTC+1, François wrote: >> >> I haven’t tried SAGE_INSTALL_GCC=no on linux or using clang >> for a full build on linux. Just one packages here and there. >> >> And yes you cann

Re: [sage-devel] Re: openblas segfault?

On Monday, September 26, 2016 at 11:23:49 PM UTC+2, Jonathan Bober wrote: > > On Mon, Sep 26, 2016 at 10:10 PM, Jean-Pierre Flori > wrote: > >> I suspect that perhaps the copy I have the works is working because I >>> built it as sage 7.3 at some point with SAGE_ATL

Re: [sage-devel] Re: [sagemath-admins] trac not responding

On Monday, September 26, 2016 at 12:02:36 PM UTC+2, Dima Pasechnik wrote: > > > > On Monday, September 26, 2016 at 9:04:08 AM UTC, Volker Braun wrote: >> >> Somebody killed unauthorized git:// over the weekend... incorrect >> firewall rule? >> > > It was William, I suppose. > Actually, disabling

Re: [sage-devel] Re: openblas segfault?

On Monday, September 26, 2016 at 9:06:17 PM UTC+2, Michael Orlitzky wrote: > > On 09/26/2016 03:03 PM, 'Martin R' via sage-devel wrote: > > > > Is there a quick fix? > > > > To get something usable, try > > ./configure --with-blas=atlas > > before running "make". I had a similar problem:

Re: [sage-devel] Re: openblas segfault?

On Monday, September 26, 2016 at 8:42:26 PM UTC+2, Jonathan Bober wrote: > > I suspect that perhaps the copy I have the works is working because I > built it as sage 7.3 at some point with SAGE_ATLAS_LIB set and then rebuilt > it on the develop branch, which didn't get rid of the atlas symlinks

Re: [sage-devel] Re: openblas segfault?

On Monday, September 26, 2016 at 11:47:00 AM UTC+2, Jonathan Bober wrote: > > On Mon, Sep 26, 2016 at 9:44 AM, Dima Pasechnik > wrote: > >> >> >> On Monday, September 26, 2016 at 2:22:51 AM UTC, Jonathan Bober wrote: >>> >>> I recompiled with gcc 6.1.0, and get the same segfault. I did a ./sage

[sage-devel] Re: Upgrade to Singular 4.x

Hi all, It seems we are left with only one failing doctest, which just looks like a different but potentially valid answer: https://trac.sagemath.org/ticket/17254#comment:364 Does any one knows enough about resolution of singularities to validate the new answer? Best, JP -- You received this

[sage-devel] Re: Add psutil as standard package

[x] I agree, let's make psutil standard -- 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 post to this group, send em

[sage-devel] Re: Upgrade to Singular 4.x

> P.S.: my test build in debug mode just failed, although everything works > fine in normal mode, surely just some linking flags missing. > Or yes now it does. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

[sage-devel] Upgrade to Singular 4.x

Dear all, Finally the upgrade from Singular 3.x to 4.x is up for review at: * https://trac.sagemath.org/ticket/17254 Best, JPF P.S.: my test build in debug mode just failed, although everything works fine in normal mode, surely just some linking flags missing. -- You received this message bec

[sage-devel] Re: [Yet again] Sage's R vs system's R

By the way I've got all we need for the upgrade. Just got to put it into a branch. -- 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...@googlegr

[sage-devel] Re: [Yet again] Sage's R vs system's R

On Saturday, August 20, 2016 at 9:15:23 PM UTC+2, Emmanuel Charpentier wrote: > > > Le samedi 20 août 2016 19:46:45 UTC+2, Jean-Pierre Flori a écrit : >> >> >> >> On Saturday, August 20, 2016 at 7:44:15 PM UTC+2, Jean-Pierre Flori wrote: >>> >>&

[sage-devel] Re: trac down?

Nevermind, it seems up. On Saturday, August 20, 2016 at 7:47:17 PM UTC+2, Jean-Pierre Flori wrote: > > trac down? > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails fro

[sage-devel] trac down?

trac down? -- 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 post to this group, send email to sage-devel@googlegroups.co

[sage-devel] Re: [Yet again] Sage's R vs system's R

On Saturday, August 20, 2016 at 7:44:15 PM UTC+2, Jean-Pierre Flori wrote: > > > > On Saturday, August 20, 2016 at 7:05:27 PM UTC+2, leif wrote: >> >> Emmanuel Charpentier wrote: >> > While trying my hand <https://trac.sagemath.org/ticket/20523&g

[sage-devel] Re: [Yet again] Sage's R vs system's R

On Saturday, August 20, 2016 at 7:05:27 PM UTC+2, leif wrote: > > Emmanuel Charpentier wrote: > > While trying my hand at > porting > > R 3.3.1 to Sage (needs_review, by the way), I found this in the > > current R Installation and Administration manual

[sage-devel] Re: Logging and optional tests

On Wednesday, August 17, 2016 at 5:08:00 PM UTC+2, Simon King wrote: > > Hi Vincent, > > On 2016-08-17, Vincent Delecroix <20100.d...@gmail.com > > wrote: > > +1: if meataxe is a great improvement for basic arithmetic ... > > See #12103. Multiplication of 2000x2000 matrices over GF(125) impro

[sage-devel] Re: Sage depends on (system) libvpx?!

On Tuesday, August 16, 2016 at 5:29:52 PM UTC+2, Luca De Feo wrote: > > > But if we want to migrate to using system libs why not let gd use > whatever it wants! > > Well, in that case we should use system gd, shouldn't we? > Yes indeed. And if we don't use the system one and build our own, let

[sage-devel] Re: Sage depends on (system) libvpx?!

On Tuesday, August 16, 2016 at 4:36:03 PM UTC+2, Luca De Feo wrote: > > After a system upgrade my built-from-source sage install started > crashing with the log message > > ImportError: libvpx.so.3: cannot open shared object file: No such > file or directory > > and indeed my system updat

Re: [sage-devel] fplll 5.0 in sage

Yes! Did you open a ticket for this? -- 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 post to this group, send email to

Re: [sage-devel] Re: Issues when building Sage with --with-mp=gmp

On Thursday, August 4, 2016 at 11:37:57 AM UTC+2, Erik Bray wrote: > > On Thu, Aug 4, 2016 at 11:35 AM, Erik Bray > wrote: > > On Thu, Aug 4, 2016 at 11:17 AM, leif > > wrote: > >> Jean-Pierre Flori wrote: > >>> On Thursday, August 4,

Re: [sage-devel] Issues when building Sage with --with-mp=gmp

On Thursday, August 4, 2016 at 11:07:38 AM UTC+2, Erik Bray wrote: > > On Sun, Jul 31, 2016 at 12:14 AM, leif > > wrote: > > To not hijack Erik's original thread on GMP/MPIR-related issues with > > /Singular on Cygwin/, this is a follow-up concerning just building Sage > > with its GMP packag

[sage-devel] Re: Sage on Bash on Ubuntu on Windows

On Wednesday, August 3, 2016 at 11:03:50 AM UTC+2, leif wrote: > > VulK wrote: > > On the topic of performances I just came across this post on phoronix: > > > http://www.phoronix.com/scan.php?page=article&item=windows-10-lxcore&num=1 > > > > TL;DR: benchmarks give surprisingly good performa

Re: [sage-devel] Re: Issues when building Sage with --with-mp=gmp

I think that I some point I wanted to support switching btw GMP and MPIR and then someone convinced me it was hopeless. The only supported solution should be to distclean, reconfigure, rebuild. If that does not work, we should fix it. As far as error are concerned, I remember that MPIR and GMP be

[sage-devel] Re: So...who are the Singular experts?

On Thursday, July 28, 2016 at 5:52:43 PM UTC+2, Nils Bruin wrote: > > > With a little luck you can get all this by just setting SAGE_DEBUG=yes > when you build singular, but I'd expect that it has bitrotted by now and > would need some loving attention to get it working again. > I think it stil

Re: [sage-devel] So...who are the Singular experts?

And at some point I had to disable omGetBackTrace: https://trac.sagemath.org/ticket/15679 -- 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...@g

Re: [sage-devel] So...who are the Singular experts?

There is also https://groups.google.com/forum/#!forum/libsingular-devel -- 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

[sage-devel] Re: So...who are the Singular experts?

On Thursday, July 28, 2016 at 4:32:29 PM UTC+2, Erik Bray wrote: > > ...and in particular, are any omalloc experts watching this list? > > I ask because my current issue in the Cygwin port of Sage is a > segfault that's occurring in Singular during a routine memory > deallocation of GMP integers

Re: [sage-devel] NTL new.h patch - singular-related - details?

I tried to do archeology once for this one and found nothing conclusive... By the way, I've forwarded all of our patches/hackery to Victor Shoup some monthes/years ago and he said he'll try to integrate them. Maybe it's time to politely ask once again about what has not been integrated (e.g. shi

Re: [sage-devel] Building Sage on top of GMP

On Monday, May 9, 2016 at 11:48:43 AM UTC+2, Jeroen Demeyer wrote: > > Did you use the GCC from the system or from Sage? (to verify: does > $SAGE_ROOT/local/bin/gcc exist?) > Hum, yes there is. A 'make clean' was surely not enough to clean up my setup, doing 'make distclean' right now. -- Yo

[sage-devel] Building Sage on top of GMP

Hi all, I was trying to build Sage (trac/develp) on top of GMP using the configure flag. The doc failed to build (unrelated) but when I typed 'make' again it decided to rebuild GMP. Did anyone encounter the same issue (or tried to use GMP)? Best, JP -- You received this message because you ar

[sage-devel] Re: SageMath for Windows installer

On Friday, March 25, 2016 at 11:37:56 AM UTC+1, Luca De Feo wrote: > > I guess this is relevant: > https://blog.docker.com/2016/03/docker-for-mac-windows-beta/ > > Shall we sign up for the private beta? > Sure! In particular "Faster and more reliable: no more VirtualBox!", ok there is some virt

Re: [sage-devel] Re: SageMath for Windows installer

I'll bring a laptop with Windows 7 installed next week at Cernay. -- 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 post

[sage-devel] Re: Weber polynomials

Note that PARI should be able to compute such polynomials as well. If not most of the needed code should be there. (There is for sure for the j-invariant, not sure exactly what other invariants are implemented right now.) Have a look at what Hamish Ivey-Law added for modular and class polynomials

[sage-devel] Re: Weber polynomials

Or rather, just opened a ticket :/ On Monday, March 7, 2016 at 1:40:44 PM UTC+1, Jean-Pierre Flori wrote: > > Actually, I also wrote minimal bindings at that time: > http://trac.sagemath.org/ticket/11809 > > On Sunday, March 6, 2016 at 4:48:30 PM UTC+1, Jean-Pierre Flori wrote: &

[sage-devel] Re: Weber polynomials

Actually, I also wrote minimal bindings at that time: http://trac.sagemath.org/ticket/11809 On Sunday, March 6, 2016 at 4:48:30 PM UTC+1, Jean-Pierre Flori wrote: > > Old ticket: > http://trac.sagemath.org/ticket/11807 > There is no bindings there though. > Maybe there is anot

Re: [sage-devel] Re: Weber polynomials

On Monday, March 7, 2016 at 1:02:10 PM UTC+1, Bill Hart wrote: > > > > On Saturday, 5 March 2016 18:11:20 UTC+1, William wrote: >> >> Relevant: Sage has a Weber class polynomial database that David Kohel >> wrote: >> >> https://www.math.aau.at/user/cheuberg/sage/doc/6.10.beta3/en/reference/

[sage-devel] Re: Weber polynomials

Old ticket: http://trac.sagemath.org/ticket/11807 There is no bindings there though. Maybe there is another ticket with bindings... And it is an old style spkg. On Sunday, March 6, 2016 at 10:26:36 AM UTC+1, David Kohel wrote: > > Hi, > > To extend beyond a pre-computed database, I suggest linking

Re: [sage-devel] Sage problem with "no more variables available"

I must admit I'm getting the same issue and am investigating this when I have spare time. It might be an internal PARI issue eating up all its variables slots when initializing finite fields. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To un

Re: [sage-devel] interrupt.pyx on PyPi?

On Tuesday, February 2, 2016 at 10:35:27 AM UTC+1, Jeroen Demeyer wrote: > > On 2016-02-02 10:16, 'Martin R. Albrecht' via sage-devel wrote: > > I guess this ends my plan to just > > > >pip install -r requirements.txt > > I'm not sure it does. I have no idea what pip install $FOO actually

Re: [sage-devel] GF(16,'x') when we do not care about the 'x'

On Thursday, January 21, 2016 at 3:26:55 AM UTC+1, William wrote: > > On Wed, Jan 20, 2016 at 6:20 PM, William Stein > wrote: > > Nils -- many thanks for your post explaining the longterm perspective > > and underlying reasons why things are the way they are. > > > > I mentioned this thread

[sage-devel] Re: Compiling of Sage on cygwin64 failed on package rpy2-2.7.5

On Thursday, January 14, 2016 at 2:43:32 PM UTC+1, Travis Scrimshaw wrote: > > > On Thursday, January 14, 2016 at 5:42:43 AM UTC-8, Travis Scrimshaw wrote: >> >> That did now work for me. >> > > That did not work for me. > You should (at least) put back the part to link to libreadline. I don't

[sage-devel] Re: Compiling of Sage on cygwin64 failed on package rpy2-2.7.5

On Thursday, January 14, 2016 at 10:04:52 AM UTC+1, Jean-Pierre Flori wrote: > > I see > > #if (defined(Win32) || defined(Win64))/* R instance as a global */Rstart > Rp;#endif > in src/rinterface/_rinterface.c. > That sounds fishy for Cygwin. > > > It looks like: h

[sage-devel] Re: Compiling of Sage on cygwin64 failed on package rpy2-2.7.5

I see #if (defined(Win32) || defined(Win64))/* R instance as a global */Rstart Rp;#endif in src/rinterface/_rinterface.c. That sounds fishy for Cygwin. It looks like: http://trac.sagemath.org/ticket/16089 And that the cygwin patch was ill porte here: http://trac.sagemath.org/ticket/19638 Note

[sage-devel] Re: sagenb and pycrypto

On Wednesday, January 13, 2016 at 3:49:45 AM UTC+1, Steven Trogdon wrote: > > I have 7.0.beta3 installed so at some point in going from 6.10 -> 7.0.x I > had to > > make distclean && make > > However, in starting the notebook the warning from > local/lib/python2.7/site-packages/Crypto/Util/num

Re: [sage-devel] Using pyximport with Sage

On Friday, December 4, 2015 at 10:48:28 AM UTC+1, Jeroen Demeyer wrote: > > On 2015-12-03 23:39, Jean-Pierre Flori wrote: > > So my questions are: > > * why does Cython complains whereas it was able to find the pxd file > > (just next to the pxi file)? > Becau

Re: [sage-devel] Using pyximport with Sage

; Could you share a "minimal non-working example" with us? > > Nathann > > On 3 December 2015 at 23:39, Jean-Pierre Flori > wrote: > > Dear all, > > > > I'm trying to make an easily distributable small package for Sage. > > Basically I&#x

[sage-devel] Using pyximport with Sage

Dear all, I'm trying to make an easily distributable small package for Sage. Basically I'd like the user to untar the files in some directory, launch Sage, run "import bla" or "load("bla.???")" and voilà. I need to compile a bunch of pyx files and it does not seem that crafting a spyx file and l

[sage-devel] Re: Who uses SAGE64

On Monday, November 30, 2015 at 2:18:09 AM UTC+1, John H Palmieri wrote: > > > > On Sunday, November 29, 2015 at 1:47:26 PM UTC-8, Volker Braun wrote: >> >> François asked me whether we still use the SAGE64 sections that are >> copy-pasted into many spkg-install files; All I know is that no buil

Re: [sage-devel] Sage bdist changes (OSX El Capitan) Jupiter Notebook doesn't work

On Thursday, November 26, 2015 at 11:44:20 AM UTC+1, Christian Nassau wrote: > > On 26.11.2015 10:31, Volker Braun wrote: > > Yes, thats because Apple decided (in their infinite wisdom) to not > > include openssl headers in El Capitan, so we can't link against OSX's > > openssl library even th

[sage-devel] Re: [mpir-devel] Re: MPIR division bug fixed

On Friday, November 13, 2015 at 12:34:41 PM UTC-8, Bill Hart wrote: > > > > On 13 November 2015 at 19:10, Jean-Pierre Flori > wrote: > >> >> >> On Friday, November 13, 2015 at 9:40:27 AM UTC-8, Bill Hart wrote: >>> >>> Not in the published

[sage-devel] Re: [mpir-devel] Re: MPIR division bug fixed

On Friday, November 13, 2015 at 9:40:27 AM UTC-8, Bill Hart wrote: > > Not in the published divide-and-conquer algorithm, no. > > There was a bug in the implementation of the new basecase algorithm, which > was not published, nor very important. On most machines it was switched > off. And even

[sage-devel] Re: MPIR division bug fixed

Hi Bill, Do you mean there was an issue in your new division algorithm? Best, JP -- 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...@googlegro

[sage-devel] Re: Babai graph isomorphism and Sage

On Thursday, November 12, 2015 at 6:00:00 PM UTC-8, kcrisman wrote: > > Surely many of you have seen the blogosphere erupt with a nearly P > algorithm for graph isomorphism. I don't have any sense as to whether this > is an actually implementable one that would be faster than e.g. nauty, but

[sage-devel] Thread boosting in NTL

Hi Victor, I plan to work on the sage ntl interface (which was written before cython supported c++) during sage days 70 in November. Hopefully I ll also look into enabling threading and exceptions. Best, JP -- You received this message because you are subscribed to the Google Groups "sage-de

Re: [sage-devel] Porting SageMath to Windows 64

On Friday, October 9, 2015 at 12:27:05 AM UTC+2, William wrote: > > > > On Thursday, October 8, 2015, Jean-Pierre Flori > wrote: > >> >> >> On Thursday, October 8, 2015 at 9:10:17 PM UTC+2, William wrote: >>> >>> >>> >>> O

Re: [sage-devel] Porting SageMath to Windows 64

On Thursday, October 8, 2015 at 9:10:17 PM UTC+2, William wrote: > > > > On Thursday, October 8, 2015, David Joyner > wrote: > >> On Thu, Oct 8, 2015 at 2:58 PM, William Stein wrote: >> > >> > >> > On Thursday, October 8, 2015, David Joyner wrote: >> >> >> >> Before this thread drops off the r

[sage-devel] Re: Porting SageMath to Windows 64

On Wednesday, October 7, 2015 at 11:27:25 PM UTC+2, Bill Hart wrote: > > OK, after more reading I find that these are the main benefits of MSYS2 > over Cygwin: > > * Support for interop with mingw-w64 built packages. > * Ability to switch from MSYS to MinGW mode by setting an environment > vari

[sage-devel] Re: Porting SageMath to Windows 64

On Wednesday, October 7, 2015 at 8:08:30 PM UTC+2, Bill Hart wrote: > > > > On Wednesday, 7 October 2015 19:54:30 UTC+2, Dima Pasechnik wrote: >> >> >> >> On Wednesday, 7 October 2015 07:35:22 UTC-7, Bill Hart wrote: >>> >>> HI all, >>> >>> William Stein recently bemoaned the fact that SageMath c

Re: [sage-devel] Porting SageMath to Windows 64

On Wednesday, October 7, 2015 at 8:03:15 PM UTC+2, Bill Hart wrote: > > > > On Wednesday, 7 October 2015 19:48:54 UTC+2, bluescarni wrote: >> >> PARI requires (required?) sizeof(mp_limb_t)==sizeof(void*), which is not >> guaranteed and not enforceable by PARI (as it's up to GMP to decide what >

Re: [sage-devel] Porting SageMath to Windows 64

On Wednesday, October 7, 2015 at 6:35:36 PM UTC+2, bluescarni wrote: > > >>> * PARI which assumes that sizeof(long) == sizeof(void*), there is an >>> experimental branch fixing this: >>> http://pari.math.u-bordeaux.fr/archives/pari-dev-1505/msg00021.html >>> >> >> I am using Pari (not GP) today

Re: [sage-devel] Porting SageMath to Windows 64

On Wednesday, October 7, 2015 at 6:23:21 PM UTC+2, Bill Hart wrote: > > > > On Wednesday, 7 October 2015 17:15:14 UTC+2, Jeroen Demeyer wrote: >> >> Is there any reason to assume that porting using MSYS2 is easier than >> porting using Cygwin? Because the latter is already hard enough. >> > > C

Re: [sage-devel] Porting SageMath to Windows 64

As far as I remember, apart from the lack of POSIX compatibility on Windows/MSYS, the main obstacle to "natively" compile Sage on Windows 64 were: * PARI which assumes that sizeof(long) == sizeof(void*), there is an experimental branch fixing this: http://pari.math.u-bordeaux.fr/archives/pari-d

[sage-devel] Re: FLINT/NTL benchmarks

Hi all, On Monday, October 5, 2015 at 4:18:27 AM UTC+2, Victor Shoup wrote: > > Thanks for the feedback, Bill! A bit of friendly competition is always a > good thing :-) > > I've been looking into SIMD for small prime FFT's...unfortunately, there > is currently > no CPU out there that supports

[sage-devel] Re: Docs: Symbols and `self`

Hi all, Slightly off-topic, but before deciding whether we use LaTeX or not, it would be nice to document how to use latex/tt font in the doc. Each time I happen to write some doc I cannot remember what backquotes and double backquotes do and you have to look deep inside the rest/sphinx doc to

Re: [sage-devel] Recompile .pyx when its .cc dependency changed

On Tuesday, September 22, 2015 at 1:16:46 PM UTC+2, Nathann Cohen wrote: > > > This works > > > > sage: !touch my_file.pyx > > sage: %runfile my_file.pyx > > Indeed, but I wouldn't mind if it were automatic somehow :-/ > > Nathann > Isn't it possible to add some distutils directive to trac

[sage-devel] Re: What can we assume about our C compiler

On Monday, September 21, 2015 at 1:47:17 PM UTC+2, Nathann Cohen wrote: > > Hello everybody, > > What can we assume on our C compiler? Is it always gcc? Is it always > recent? > > I guess the configure script is made to check it is recent enough and provides what is needed to build Sage. Or a

Re: [sage-devel] Coercion between finite fields

On Thursday, September 17, 2015 at 12:24:07 PM UTC+2, Jeroen Demeyer wrote: > > On 2015-09-17 11:56, Volker Braun wrote: > > Two comments: > > > > A) There is no such thing as "different finite fields of the same size > > with the same generator name" > > Of course there is: > > sage: GF(8,

Re: [sage-devel] Coercion between finite fields

Hi, I guess one of the issue is that there is no canonical map between two different representations of the same finite field (so no coercion). In your case it is slightly more specific as it might be the case that K1 and K2 are constructed in the same exact way (expect for the string 'a' and '

Re: [sage-devel] Re: *.math.washington.edu hardware resources

Hi all, I can also help if needed. Maybe that would make the french admins count too high :) Best, JP On Wednesday, September 16, 2015 at 4:26:08 PM UTC+2, William wrote: > > Hi, > > A concrete first task is to add everybody on the following list to the > sagemath-admins mailing list (by track

[sage-devel] Re: What is "long time", what should not be tested

# very long time ? :) On Tuesday, September 15, 2015 at 12:05:25 PM UTC+2, Nathann Cohen wrote: > > Hello everybody, > > In my current patches I often meet some threshold in the doctests I add. > Instantaneous doctests are okay, doctests which last a few seconds are "# > long time", but because

Re: [sage-devel] Re: Integer from mpz_t

On Wednesday, August 19, 2015 at 12:36:07 PM UTC+2, vdelecroix wrote: > > > > On 19/08/15 12:31, Jean-Pierre Flori wrote: > > > > > > On Wednesday, August 19, 2015 at 12:21:36 PM UTC+2, vdelecroix wrote: > >> > >> Note that all the solu

Re: [sage-devel] Re: Integer from mpz_t

On Wednesday, August 19, 2015 at 12:21:36 PM UTC+2, vdelecroix wrote: > > Note that all the solutions given will *copy* the mpz_t to the Integer. > Is that what you want? It is also possible to avoid the copy if it is > worth it (i.e. you have a big integer). > And one shall not use PY_NEW bu

[sage-devel] Re: Integer from mpz_t

On Wednesday, August 19, 2015 at 11:19:30 AM UTC+2, Ralf Stephan wrote: > > Given an mpz_t, how to most effectively create an Integer? > The best I can come up with is through the string representation. > Or, of course, by patching integer.pyx. > > Am I missing something? > > From Cython you can

[sage-devel] Re: MPIR 2.7.0 released

Trac ticket for updating at http://trac.sagemath.org/ticket/18790#ticket. (Currently empty.) -- 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...

[sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report

OS X in VM's? Is that legal? Maybe only on OS X hardware? -- 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 post to this

Re: [sage-devel] The future of polybori

Your plan does look good to me Martin. Just note it won&t be trivial. -- 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 p

[sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report

sage-devel or sage-support (or sage-install or sage-apple or sage-osx :) -- 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. T

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

Le lundi 8 juin 2015 18:02:46 UTC+2, Stefan Auracher a écrit : > > How to do this ? > > I found in ~/sage-6.7/src/module_list.py > > Extension('sage.rings.polynomial.pbori', > sources = ['sage/rings/polynomial/pbori.pyx'], > libraries=['polybori-' + polybori_major_vers

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

Le lundi 8 juin 2015 14:22:20 UTC+2, Jean-Pierre Flori a écrit : > > > > Le lundi 8 juin 2015 13:54:01 UTC+2, Stefan Auracher a écrit : >> >> In the past I had the same experience. I did it but in the last years, >> but it was really difficult. But recently I t

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

Le lundi 8 juin 2015 13:54:01 UTC+2, Stefan Auracher a écrit : > > In the past I had the same experience. I did it but in the last years, but > it was really difficult. But recently I tried an install of cygwin with the > setup-x86_64.exe --no-admin switch and it worked very well wihout any >

[sage-devel] Re: sage-6.7 build failed on Cygwin64 for python-2.7.8 No module named crypt

On Friday, June 5, 2015 at 2:49:40 PM UTC+2, Stefan Auracher wrote: > > the logfile > ~/sage-6.7/logs/pkgs/python-2.7.8.log > at the very end after make[3]: Leaving directory > '/home/XX/sage-6.7/local/var/tmp/sage/build/python-2.7.8/src' > failed with: > > Installing valgrind suppressio

[sage-devel] Re: Trac git interface half broken?

It seems the trac/git failure was not caused by the lack of space on /tmp as it is still dysfunctional. -- 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

[sage-devel] Re: Trac error

Thanks. On Thursday, May 21, 2015 at 9:29:18 PM UTC+2, Eric Gourgoulhon wrote: > > > > Le jeudi 21 mai 2015 19:22:53 UTC+2, Volker Braun a écrit : >> >> fixed >> >> > Thanks! > > Eric. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubsc

[sage-devel] Trac git interface half broken?

Dear all, In case the one in charge was not aware, it seems the trac git interface is half broken. For instance, http://git.sagemath.org/sage.git/diff/?id=2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f shows no diff. Best, JP -- You received this message because you are subscribed to the Google G

[sage-devel] Is anyone trying to build Sage on old x86 without MMX?

In http://trac.sagemath.org/ticket/18027, Jeroen would like to drop (partly) drop suppor for such CPUs when signals are received. I guess what would happen is that an additional SIGILL or something like that will happen because of the unsupported MMX-only FPU reset asm instruciton, but I did not

Re: [sage-devel] Re: Is there an online index of the standard packages shipped in Sage?

Great news! I guess we can finally have a "make donwload" target which only downloads standard packages now. And maybe a simple way to cleanup the upstream directory, see #16327. On Sunday, May 17, 2015 at 8:30:04 AM UTC+2, Nathann Cohen wrote: > > > We were not talking about a catalog, but an ad

Re: [sage-devel] Re: Bug with vars()?

I unpacked the sage 6.6 tarball and ran make. I'll have some trouble posting the exact output here as the machine is not connected to the network, but basically: * I'm on an amd64 Ubuntu 14.04.2 LTS. * I launch: sage * I type at Sage's prompt: vars() * I get: """ /blablabla/pretty_print.py:147: D

[sage-devel] Bug with vars()?

Dear all, My Sage 6.6 install quits after printing a depreciation warning message when I issue: sage: vars() Same is true for at least globals(). Any clue on what's going on? Best, JP -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscr

[sage-devel] Re: pynac may require C++11 in Sage

Latest NTL releases also require C++11. -- 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 post to this group, send email

Re: [sage-devel] Non-Sage C code in the Sage library

On Friday, April 24, 2015 at 10:42:12 AM UTC+2, John Cremona wrote: > > On 24 April 2015 at 09:37, John Cremona > > wrote: > > Who is the author of hyperellfrob? > > OK, I found it (it is actually called hypellfrob): David Harvey. > David, if you are listening -- any comments? > And availabl

[sage-devel] Cythonization of Sage extensions, wildcards in module_list.py and Cython directives

Dear all, It seems we're shifting from the original way we were building Cython extensions where each extension was listed in module_list.py to use wildcards in module_list.py. See #7987 and #15410 for wide coverage tickets, and e.g. #17767 for more focused ones. This is problematic when some

<    1   2   3   4   5   6   7   8   9   >