[sage-devel] Re: CC vs MPC

On Tuesday, April 7, 2015 at 8:43:58 PM UTC+2, Jean-Pierre Flori wrote: > > > > On Tuesday, April 7, 2015 at 6:56:56 PM UTC+2, vdelecroix wrote: >> >> Hello, >> >> We currently ship two implementations of floating point complex numbers: >> - ComplexFi

[sage-devel] Re: CC vs MPC

On Tuesday, April 7, 2015 at 6:56:56 PM UTC+2, vdelecroix wrote: > > Hello, > > We currently ship two implementations of floating point complex numbers: > - ComplexField: home made implementation based on two mpfr for the > real and imaginary parts > - MPComplexField: implementation based o

[sage-devel] Re: For french readers

y opposed, e.g. > http://www.joelonsoftware.com/articles/fog69.html > > > > On Tuesday, March 31, 2015 at 12:11:34 PM UTC+2, Jean-Pierre Flori wrote: >> >> Let's replace Python by Julia :p >> >> >> http://lavieestmaloptimisee.blogspot.fr/2015/03/les-informaticien

[sage-devel] For french readers

Let's replace Python by Julia :p http://lavieestmaloptimisee.blogspot.fr/2015/03/les-informaticiens-meprisent.html?view=classic -- 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

Re: [sage-devel] Proposal: make _cmp_c_impl() override __cmp__()

The few times I played with comparison functions, I found what we have quite confusing, especially the discrpancy between Python and Cython classes, so any simplification would be welcomed. And if it also eases the transition towards Python 3 that would be great. -- You received this message b

Re: [sage-devel] [Debian] Strange crash in ECL

Not really related but it seems ECL saw an update! On Wednesday, February 25, 2015 at 10:43:28 PM UTC+1, François wrote: > > On 02/26/15 10:30, Julien Puydt wrote: > > Hi, > > > > Le 25/02/2015 10:56, Julien Puydt a écrit : > >> it is a strange problem I have : using either debian's ecl or >

[sage-devel] Re: [ARM] sage 6.5

On Monday, February 23, 2015 at 3:34:08 PM UTC+1, Dima Pasechnik wrote: > > On 2015-02-23, Julien Puydt > wrote: > > Le 23/02/2015 15:05, Julien Puydt a écrit : > >> Le 23/02/2015 14:27, Julien Puydt a écrit : > >>> That will take some time though : this box isn't fast. And I work on > it >

Re: [sage-devel] Re: [ARM] sage 6.5

On Saturday, February 21, 2015 at 5:25:07 PM UTC+1, Volker Braun wrote: > > The atlas build script just aborts with SAGE_ATLAS_ARCH=base, nothing else > to see here. > > Pointing to a specific location for the atlas library isn't going to be > much use in a binary that we distribute. > > > > On

Re: [sage-devel] sage-6.5.1?

On Friday, February 20, 2015 at 4:29:38 PM UTC+1, John Cremona wrote: > > On 20 February 2015 at 15:10, Vincent Delecroix > <20100.d...@gmail.com > wrote: > > Hello, > > > > We do have two very serious critical bug with the new version 6.5, > namely > > * #17806 (MPIR compilation) > > *

[sage-devel] Dashes in software name or version number

Dear all, Is this still a problem? 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...@googlegroups.com. To post to this group, send

[sage-devel] Re: GMP tarball not mirrored

Thanks! On Tuesday, January 13, 2015 at 4:30:48 PM UTC+1, Volker Braun wrote: > > Done! > > On Tue, Jan 13, 2015 at 4:20 PM, Jean-Pierre Flori > wrote: > > Thanks! > > I also added Volker just in case. > > > > On Tuesday, January 13, 2015 at

[sage-devel] Re: GMP tarball not mirrored

Thanks! I also added Volker just in case. On Tuesday, January 13, 2015 at 4:15:09 PM UTC+1, Dima Pasechnik wrote: > > On 2015-01-13, Jean-Pierre Flori > wrote: > > GMP was added as an optional package in > > http://trac.sagemath.org/ticket/12661. > > > > Who

[sage-devel] GMP tarball not mirrored

GMP was added as an optional package in http://trac.sagemath.org/ticket/12661. Who should I CC? -- 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+unsubs

[sage-devel] Re: Bug Days?

On Thursday, January 8, 2015 at 4:34:22 PM UTC+1, William wrote: > > Hi, > > Would anybody be interested in helping me to organize a bug days > workshop sometime in the next few months? > I have plenty of funding for this for US people and can scrounge up > some funds for some non-US people.

[sage-devel] Re: Build error for sage 6.4 beta 5 under cygwin64

On Friday, January 9, 2015 at 12:30:16 PM UTC+1, Jean-Pierre Flori wrote: > > > > On Friday, January 9, 2015 at 9:49:52 AM UTC+1, Sebastien Gouezel wrote: >> >> The webpage http://trac.sagemath.org/wiki/Cygwin64Port indicates that >> sage can now be built under

[sage-devel] Re: Build error for sage 6.4 beta 5 under cygwin64

On Friday, January 9, 2015 at 9:49:52 AM UTC+1, Sebastien Gouezel wrote: > > The webpage http://trac.sagemath.org/wiki/Cygwin64Port indicates that > sage can now be built under cygwin64 almost out of the box. So, I tried, > but I failed... > > Here are the problems I encountered, maybe someone

[sage-devel] Re: How's tkinter on Macs?

Sorry, I meant the milestone. -- 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-de

[sage-devel] Re: How's tkinter on Macs?

On Wednesday, January 7, 2015 5:02:31 AM UTC+1, Nathan Dunfield wrote: > > I agree: Tkinter works out-of-the box on OS X with any recent source or >>> binary release of Sage. >>> >>> Can you review that ticket, then? I have no experience with Tkinter >> myself. >> > > Sure, but what does tha

Re: [sage-devel] Re: Cygwin(64) port status

On Tuesday, January 6, 2015 4:02:45 PM UTC+1, Jean-Pierre Flori wrote: > > > > On Tuesday, January 6, 2015 3:51:29 PM UTC+1, John Cremona wrote: >> >> By the way, there is discussion of building Pari under Cygwin 64 on >> the pari-dev list; bugs are being

Re: [sage-devel] Re: Cygwin(64) port status

On Tuesday, January 6, 2015 3:51:29 PM UTC+1, John Cremona wrote: > > By the way, there is discussion of building Pari under Cygwin 64 on > the pari-dev list; bugs are being discovered and fixed as I type. > > Great news! My last findings were that PARI behaved very badly on Cygwin64. For exam

Re: [sage-devel] Re: GF(3) but GF(9,'x')

On Tuesday, December 30, 2014 1:40:29 PM UTC+1, Bruno Grenet wrote: > > > Le 30/12/2014 13:31, Jean-Pierre Flori a écrit : > > Anyhow, the above looks ugly. How about > >> sage: F. = GF(3, 5) >> >> and the following should also lead to the same thing:

[sage-devel] Re: GF(3) but GF(9,'x')

Anyhow, the above looks ugly. How about > sage: F. = GF(3, 5) > > and the following should also lead to the same thing: > > sage: F. = GF(3^5) > > We already have that, or am I missing something? > Dima > > > > > Peter > > > > > > Op dinsdag 30 december 2014 12:35:30 UTC+1 schreef Dim

[sage-devel] Re: GF(3) but GF(9,'x')

On Tuesday, December 30, 2014 12:35:30 PM UTC+1, Dima Pasechnik wrote: > > On 2014-12-30, Nathann Cohen > wrote: > > I wondered about this syntax. You can build a finite field from a > > prime number with GF(p), but if what you have is a prime power you > > should write GF(q,'x') instead. > >

Re: [sage-devel] GF(3) but GF(9,'x')

I would also be nice to be able to pass GF(3,3). If I ever find some time to implement it, I'll do it, but anyone can feel free to do it before I do. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivin

[sage-devel] Re: Cygwin(64) port status

Thanks to Travis, only the ATLAS patch needs review! http://trac.sagemath.org/ticket/17365 -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: where is the code for __eq__ (of ring elements)

Nathann, if you're still tens of kilometers away from the nearest pub, you might want to turn all the info here into proper documentation? On Sunday, December 28, 2014 1:45:26 AM UTC+1, Nils Bruin wrote: > > On Saturday, December 27, 2014 3:13:37 PM UTC-8, Simon King wrote: >> >> That's exactly w

[sage-devel] Re: The Sage dev scripts

On Friday, December 26, 2014 9:07:06 PM UTC+1, Dima Pasechnik wrote: > > On 2014-12-26, Volker Braun > wrote: > > --=_Part_5531_1685050387.1419616059330 > > Content-Type: multipart/alternative; > > boundary="=_Part_5532_1775001320.1419616059330" > > > > --=_Part_5532_1775

[sage-devel] Re: Cygwin(64) port status

ime to look again at Cygwin stuff soon. > > > On Thursday, December 11, 2014 6:37:33 AM UTC-8, Jean-Pierre Flori wrote: >> >> >> >> On Thursday, November 27, 2014 6:39:13 PM UTC+1, Jean-Pierre Flori wrote: >>> >>> And I forgot http://trac.sa

Re: [sage-devel] Plenty of review material out there...

On Friday, December 19, 2014 4:03:44 PM UTC+1, Bruno Grenet wrote: > > I've changed recently the status of a ticket to "needs review" since I > think it is not relevant anymore, and I wanted it to be closed. I now > guess it is not the right approach... What should I do in such a case? > > Put

[sage-devel] Re: Problem building on openSUSE

On Wednesday, December 17, 2014 3:10:36 PM UTC+1, Simon King wrote: > > Hi Jean-Pierre, > > On 2014-12-17, Jean-Pierre Flori > wrote: > > I guess this is: > > > https://groups.google.com/forum/#!searchin/sage-devel/complex.h/sage-devel/iA3K1T8lPlQ/hyACR

[sage-devel] Re: Problem building on openSUSE

I guess this is: https://groups.google.com/forum/#!searchin/sage-devel/complex.h/sage-devel/iA3K1T8lPlQ/hyACRbExOkMJ On Wednesday, December 17, 2014 2:33:46 PM UTC+1, Simon King wrote: > > Hi! > > I just have now installed openSUSE 13.2 64bit on my laptop (it has > previously > been 12.3), and

[sage-devel] Re: Cygwin(64) port status

On Thursday, November 27, 2014 6:39:13 PM UTC+1, Jean-Pierre Flori wrote: > > And I forgot http://trac.sagemath.org/ticket/17365 and > http://trac.sagemath.org/ticket/15649 which need a little love (and as it > only affects Cygwin should be easy to review, at least if you trust

Re: [sage-devel] Re: User Survey

On Tuesday, December 9, 2014 6:25:56 PM UTC+1, William wrote: > > On Tue, Dec 9, 2014 at 9:20 AM, mmarco > > wrote: > > Yes we do, but not as completely as x86. For instance the last version > that > > has an arm binary in the download page is 5.13. > > > > The Wolfram language, which is so

[sage-devel] rest syntax

Do we have anything about that in our dev guide? Or at least a pointer to the rest/sphinx doc? e.g. http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html Every time I have to add doc I wonder whether I should use one or two backticks and so on and cannot find anything in our docs...

Re: [sage-devel] Re: User Survey

On Monday, December 8, 2014 9:53:51 PM UTC+1, mmarco wrote: > > Maybe support for arm architecture would be relevant in that respect. We do support ARM, don't we? At least I'm able to compile Sage from scratch on a Raspberry Pi and on armv7+ as well. -- You received this message because you

[sage-devel] Re: Looking for OSX buildbot

On Thursday, December 4, 2014 3:38:18 PM UTC+1, Dima Pasechnik wrote: > > On 2014-12-01, Volker Braun > wrote: > > --=_Part_3157_1040776803.1417466369538 > > Content-Type: multipart/alternative; > > boundary="=_Part_3158_1081423206.1417466369539" > > > > --=_Part_3158_108

[sage-devel] Re: Cygwin(64) port status

And I forgot http://trac.sagemath.org/ticket/17365 and http://trac.sagemath.org/ticket/15649 which need a little love (and as it only affects Cygwin should be easy to review, at least if you trust me)!!! -- You received this message because you are subscribed to the Google Groups "sage-devel"

[sage-devel] Re: Cygwin(64) port status

On Tuesday, November 25, 2014 10:46:56 PM UTC+1, mmarco wrote: > > The result of the compilation is relocatable? I mean, would it be > eventually possible to have something that windows users just unzip and > runs? Or would they always need to compile it? > I would say so, i dont really know if

Re: [sage-devel] Compilation Error sage 6.4.1 : installing package ecl-13.5.1.p0

On Wednesday, November 26, 2014 9:17:27 PM UTC+1, François wrote: > > Hi, > > A bit of a shot in the dark but could you try it from a folder with > only ascii characters? "Telechargements" instead of "Téléchargement". > It is possible that the ecl bootstrap doesn't like those characters > ver

Re: [sage-devel] Cygwin(64) port status

Note that everything gets built, but at this point I don't promise it is really functional. Cygwin32 should be almost fully functional. Cygwin64 is very far from it (e.g. PARI builds but seems completely broken: it says 131 is not prime). Anyway getting back to a point where just typing "make"

[sage-devel] Cygwin(64) port status

Hi all, With http://trac.sagemath.org/ticket/15649 and http://trac.sagemath.org/ticket/17365 which need reviews and touch Cygwin-only code we'll (almost) have support to build Sage trivially (type "make") on Cygwin (again) and Cygwin64 (for the first time). Only the MPIR update at http://trac.s

[sage-devel] Do we have a make target to clean upstream directory?

As time goes it gets bigger and bigger... -- 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 emai

[sage-devel] Re: Document patches in the patch file, not in SPKG.txt

On Monday, November 17, 2014 1:45:09 PM UTC+1, Volker Braun wrote: > > I would like to propose another change to SPKG.txt, and that is to NOT > document patches in there but in the patch file. As you might know, the > patch can have arbitrary text before the first diff hunk, anything that is > n

[sage-devel] NTL and Singular updates

Dear all, Anyone feeling like reviewing the updates to NTL 6.2.1 (http://trac.sagemath.org/ticket/16882) and Singular 3-1-7 (http://trac.sagemath.org/ticket/17184) ? It would be nice to have them in before working on the much more involved Singular 4-0-x and (surely not so hard) NTL 7.0.1 updat

Re: [sage-devel] Re: Future NTL versions and exception handling

xceptions between threads. In particular, using an > std::future for managing the return value of (or the exception thrown > within) a thread is pretty handy. > > Cheers, > > Francesco. > > On 12 November 2014 00:05, Jean-Pierre Flori > wrote: > >> >> >>

[sage-devel] Re: Future NTL versions and exception handling

s uses a zero-cost model so its > at least as fast as handling / returning some error flag. What _is_ > expensive is when an exception occurs, but in C++ you are not supposed to > use exceptions for program flow like in Python. > > > > On Tuesday, November 11, 2014 10:15:44 PM UTC, J

[sage-devel] Future NTL versions and exception handling

Dear all, As you must have noticed, Victor Shoup just released a new thread safe version of NTL. He also took the opportunity to ask me (and surely a bunch of other people) what would be expected from exception handling in NTL Currently NTL just prints something and then aborts. Note that we pa

Re: [sage-devel] Fwd: NTL v7 -- thread safety

On Tuesday, November 11, 2014 10:12:33 PM UTC+1, François wrote: > > I guess the compiler requirement will kill all the problems > we saw in #16882 which is a good thing TM. > > Sure, but will make a lot of people have to compile GCC 4.9.2 :) Could you review #16882 before we begin working on

Re: [sage-devel] Re: Should we ship vanilla upstream tarballs or stripped-down ones?

On Wednesday, November 5, 2014 2:39:15 PM UTC+1, Thierry (sage-googlesucks@xxx) wrote: > > On Wed, Nov 05, 2014 at 05:22:17AM -0800, Jean-Pierre Flori wrote: > > > > > > On Wednesday, November 5, 2014 2:17:29 PM UTC+1, Volker Braun wrote: > > > > > &

Re: [sage-devel] Re: Should we ship vanilla upstream tarballs or stripped-down ones?

On Wednesday, November 5, 2014 2:17:29 PM UTC+1, Volker Braun wrote: > > There is already a "make download". If you want you can add a "make > download-more" (or so) to also download popular optional packages... > > Doesn't make download already download everything? Or was it fixed/changed? --

[sage-devel] Should we ship vanilla upstream tarballs or stripped-down ones?

Dear all, Should we go on stripping down upstream tarballs from stuff we don't use when there is some substantial gain? See http://trac.sagemath.org/ticket/17169 (GCC) and http://trac.sagemath.org/ticket/15015 (MPIR). We can debate forever on when the gain becomes substantial in comparison with

Re: [sage-devel] SPKG Maintainers??

I agree let's get rid of this. I've updated a bunch of packages but did not feel like filling this field with my name as I couldn't promise I'll keep on maintaining the packages. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe fro

[sage-devel] Need help from someone knowing Singular

We're stuck at http://trac.sagemath.org/ticket/17184. I've also posted on Singular forum: http://www.singular.uni-kl.de/forum/viewtopic.php?f=10&t=2466&sid=01f281c0cfb23e8e420dbe49dc1a85cb Help from someone knowing Singular internals would be welcome. Best, JP -- You received this message beca

Re: [sage-devel] Why do we keep (very old) itanium binaries?

There used to be Itanium machines on the GCC Compile Farm, and I have access there, in particular for testing/developing Sage stuff. I don't now the current situation though. Actually, I am supposed to write a laius about the need for Sage portability on exotic archs/porting somehow on Windows (b

[sage-devel] Re: OSX Yosemite

Relevant? https://groups.google.com/d/msg/sage-devel/-sm2ejzcjY8/x27G0nMRdY4J On Friday, October 17, 2014 6:58:16 PM UTC+2, Volker Braun wrote: > > I upgraded my OSX buildbot, now it doesn't compile Sage any more ;-) > > Checking multilib configuration for libgcc... > Configuring stage 1 in x86_6

Re: [sage-coding-theory] Re: [sage-devel] Re: 2-year project with full-time software developer for improving coding theory in Sage

I think it would also be a good idea to get in contact with the matroids folk who got a lot of code integrated into Sage some time ago. Or even better with Eric Gourgoulhon whos currently writing a lot of code for his project and getting it integrated into Sage piece by piece. On top of that he's

Re: [sage-devel] Proposal: remove SAGE_UPGRADING

On Tuesday, September 30, 2014 10:51:05 AM UTC+2, Jeroen Demeyer wrote: > > On 2014-09-30 08:24, Jeroen Demeyer wrote: > > I certainly agree with this, but it should be said that "make" will take > > a longer time when changing packages. For example, you will see ATLAS > > being rebuilt very f

Re: [sage-devel] Proposal: remove SAGE_UPGRADING

I also agree with the removal, with the issue of ATLAS. Maybe we should switch to openblas (IIRC Clément Pernet said it is more state of the art nowadays) :) On Tuesday, September 30, 2014 9:15:59 AM UTC+2, Jeroen Demeyer wrote: > > See http://trac.sagemath.org/ticket/17072 > -- You received t

Re: [sage-devel] Re: Sage package bash?

On Saturday, September 27, 2014 10:36:14 PM UTC+2, kcrisman wrote: > > If I recall correctly sometimes one needs to use dash instead of bash on > Cygwin, but nonetheless it somehow works, maybe because dash is only > necessary when going "outside" of Sage for rebasing or something? > Yes, (appr

[sage-devel] Re: Sage package bash?

> > > 2. Dima -- do we specifically use bash features in the build scripts of > > Sage? > > Sage scripts have "!/usr/bin/env bash" all over the place. > I don't know about 'bashisms' though - one should test on a Debian system, > where bash is not essential, as they have a push to move to das

[sage-devel] Posting comments to a closed ticket empties the commit field

It seems to me it is the case. Can this be "fixed"? It's not really important as the commit is still linked in the branch field and that's the only place a human can clic. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this g

[sage-devel] Re: compiling sage 6.3 on a raspberry pi

On Monday, September 15, 2014 12:30:06 PM UTC+2, mmarco wrote: > > I have purchased one of these boards: > > > https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-LIME/open-source-hardware > > And plan to plug in it a ssd drive to allow fast swap space. I would like > to use it to compi

Re: [sage-devel] Re: compiling sage 6.3 on a raspberry pi

And maybe I spoke too fast. The build system of "Sage the distribution" is not smart enough for sure. But I seem to remember you may be able to cross compile using lmonade. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this g

Re: [sage-devel] Re: compiling sage 6.3 on a raspberry pi

On Friday, September 12, 2014 11:15:19 AM UTC+2, bluescarni wrote: > > What you want is called "cross-compilation", and in general is a > non-trivial thing to do. You have to set up a toolchain on your x86 boxes > able to compile for ARM, use it to compile SAGE and finally move the binary > ov

[sage-devel] Re: compiling sage 6.3 on a raspberry pi

Indeed it should basically work out of the box if you make some swap space available (let's say 1 gbyte). At least it used to do, possibly with a few trivial fixes (and I surely opened tickets on trac for them, also see http://trac.sagemath.org/wiki/ExoticPorts#RaspberryPirunningRaspbianarmv6wit

[sage-devel] Re: Memory leak in evaluating polynomials over finite fields

Does it also leak with older version of Sage? -- 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

[sage-devel] Re: Memory leak in evaluating polynomials over finite fields

this does not remind me of anything except http://trac.sagemath.org/ticket/3603 which is surely unrelated (different backend) and http://trac.sagemath.org/ticket/13447 but not so related either. On Wednesday, September 10, 2014 1:03:15 AM UTC+2, Volker Braun wrote: > > I was dabbling in arithme

[sage-devel] Re: Sage's debug version

On Friday, September 5, 2014 3:47:53 PM UTC+2, Volker Braun wrote: > > I don't know of a ticket, feel free to fix it. All relevant files are in > build/pkgs/singular. It seems that the debug patches conflict with the > cygwin patch. Also, the debug patches should probably be applied strictly >

[sage-devel] Re: Sage's debug version

I can help, and am surely guilty for the cygwin64 patch. Please open a ticket and I'll have a look. On Friday, September 5, 2014 3:39:34 PM UTC+2, Simon King wrote: > > Hi! > > I just tried to build a debug version of Sage on my openSuse 12.3 laptop. > However, with SAGE_DEBUG=yes, the Singular

Re: [sage-devel] Re: Compiling sage on Fedora

On Friday, September 5, 2014 11:42:21 AM UTC+2, Jori Mantysalo wrote: > > On Fri, 5 Sep 2014, Volker Braun wrote: > > > So it seems that we don't link libf77blas against libgfortran. Whats the > output of > > > > sage -sh -c "ldd local/lib/libf77blas.so" > > linux-vdso.so.1 => (0x

Re: [sage-devel] Re: speed regression testing

Hi Clément and all, On Friday, August 29, 2014 10:53:18 AM UTC+2, Clement Pernet wrote: > > Hi, > > Let me clarify a few things: > - LinBox's approach to link against numerical BLAS has never changed, and > probably will not in the > near future. > - LAPACK is not BLAS: BLAS provides optimiz

[sage-devel] Re: Is the valgrind spkg broken? Debugging help needed...

On Wednesday, September 3, 2014 4:57:19 PM UTC+2, Simon King wrote: > > Dear all, > > I just installed the valgrind spkg, did "make", and then started "./sage > --valgrind", in order to run a stress test for what I call "biseq" > (bounded integer sequences) at #15820. Eventually, I want to use

Re: [sage-devel] Re: Make ARM a supported platform

On Tuesday, September 2, 2014 3:13:09 PM UTC+2, mmarco wrote: > > >> You mean like using SAGE_ATLAS_LIB to avoid shipping a too optimized >> version of that lib? >> >> > My comment was more in the line of making sure that the resulting compiled > code does not use instructions that are not ava

Re: [sage-devel] Make ARM a supported platform

Hi Snark, Did you CC Harald? I thought he was in charge of this kind of stuff... -- 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...@googlegrou

[sage-devel] Re: Make ARM a supported platform

Cool. IIRC different kind of ARM boards have already been used by a bunch of users with success. At least I had quite no problems building Sage on a Raspberry Pi and on a Cortex A9 based board. On Monday, September 1, 2014 2:49:06 PM UTC+2, Volker Braun wrote: > > I'm proposing to make ARM a ful

[sage-devel] Re: speed regression testing

I don't know for sure, but I think linbox does not link to LAPACK (anymore?). Maybe that make a small difference already. I opened a ticket about that some monthes ago. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this grou

[sage-devel] Re: upgrade to singular 4.0 in sage?

I think one of lmonade's GSoC project was about that. But I don't think it was picked up -- 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...

Re: [sage-devel] proposal: remove python spkg and use pip instead

On Wednesday, August 27, 2014 9:11:47 PM UTC+2, Jeroen Demeyer wrote: > > On 2014-08-27 21:01, Julien Puydt wrote: > > but on a general basis people are quite welcoming of > > sensible contributions. > Depends on the project. Whenever I think a patch is good for upstream, I > do submit it ups

Re: [sage-devel] Re: How practical/useful would a native windows subset be?

On Wednesday, August 27, 2014 11:00:35 AM UTC+2, Jeroen Demeyer wrote: > > On 2014-08-27 10:22, Jean-Pierre Flori wrote: > > Note that cross-compiler running on linux and targetting mingw(64) have > > been available since mingw(64) is. > Many packages in Sage do not su

[sage-devel] Re: How practical/useful would a native windows subset be?

On Wednesday, August 27, 2014 2:13:25 AM UTC+2, Bill Hart wrote: > > I am again very interested in having Windows 64 ports of various packages. > > At the top of my list are: > > * GAP > * Singular > * Pari/GP > > Note that MinGW2 is a much better way to do this than has previously been > availa

Re: [sage-devel] Fwd: NTL version 6.2

On Tuesday, August 26, 2014 3:53:00 PM UTC+2, John Cremona wrote: > > On 26 August 2014 14:33, Julien Puydt > > wrote: > > Hi, > > > > Le 26/08/2014 14:11, John Cremona a écrit : > > > >> -- Forwarded message -- > >> From: Victor Shoup > > >> Date: 22 August 2014 04:19 >

Re: [sage-devel] Fwd: NTL version 6.2

On Tuesday, August 26, 2014 3:34:04 PM UTC+2, Snark wrote: > > Hi, > > Le 26/08/2014 14:11, John Cremona a écrit : > > -- Forwarded message -- > > From: Victor Shoup > > > Date: 22 August 2014 04:19 > > Subject: NTL version 6.2 > > To: nmbr...@listserv.nodak.edu > > > > I

[sage-devel] Re: How practical/useful would a native windows subset be?

My souvenir here is that Sage almost builds out of the box on Cygwin64 modulo some patches i posted in different tickets. It is not really funcitonnal though, last time I tried it seemed to me that Python itself was horribly broken. On Monday, August 25, 2014 4:58:56 PM UTC+2, kcrisman wrote: >

Re: [sage-devel] Re: How practical/useful would a native windows subset be?

On Monday, August 25, 2014 1:35:29 PM UTC+2, wstein wrote: > > > This reminds me of Michael Abshoff. He was supposed to port Sage to > > That was the name I was looking for I guess. And one of the posts I was thinking of: https://groups.google.com/d/msg/sage-devel/QXy_2KMbP1k/Z3cfpCieYzgJ --

[sage-devel] Re: How practical/useful would a native windows subset be?

On Monday, August 25, 2014 11:49:49 AM UTC+2, mmarco wrote: > > IIRC, GAP and Pari/GP do have a native windows version. Singular has a > cygwin version. > > El lunes, 25 de agosto de 2014 11:05:08 UTC+2, Dima Pasechnik escribió: >> >> On 2014-08-25, Dr. David Kirkby (Kirkby Microwave Ltd) < >> d

[sage-devel] Re: Crazy/dumb idea about Sage on Windows...

On Friday, August 22, 2014 2:05:44 PM UTC+2, mmarco wrote: > > > In fact, there was a GSoC proposal to write some simple GUI that would > handle the VM: check for firewall issues, open the VM's browser if there > are, and run the VM in headless mode if there are not, also handle the > actualiz

[sage-devel] Re: Equality, hashing and polynomial rings

On top of that, Python3 want have cmp anymore :) -- 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, se

[sage-devel] Re: Equality, hashing and polynomial rings

Thanks for all the answers. It seems my issues was caused by defining the _cmp_ method with the wrong number of underscores in my cython extension classes. Do you confirm that for parents defined in a usual Python class __cmp__ with two underscores should be used and for a cython extension class

[sage-devel] Re: Equality, hashing and polynomial rings

On Tuesday, August 19, 2014 9:05:15 PM UTC+2, Simon King wrote: > > Hi Jean-Pierre, > > On 2014-08-19, Jean-Pierre Flori > wrote: > > Though (non-prime) finite fields with the same order and defining > > polynomial are considered equal, I'd say the hashes shou

[sage-devel] Re: Equality, hashing and polynomial rings

I guess _cmp_ should be used for cython parents and __cmp__ for python ones. There is in parent.pyx: # Both are parents -- but need *not* have the same type. if HAS_DICTIONARY(left): r = left.__cmp__(right) else: r = left._cmp_(rig

[sage-devel] Re: Equality, hashing and polynomial rings

On Tuesday, August 19, 2014 8:26:13 PM UTC+2, Jean-Pierre Flori wrote: > > I also see that some double underscore methods rather than single > underscore ones are implemented, that might be one of the problems here. > Or the other way around... -- You received this message bec

[sage-devel] Re: Equality, hashing and polynomial rings

I also see that some double underscore methods rather than single underscore ones are implemented, that might be one of the problems here. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails fr

[sage-devel] Re: Equality, hashing and polynomial rings

On Tuesday, August 19, 2014 7:39:18 PM UTC+2, Peter Bruin wrote: > > Hi Jean-Pierre, > > I'm currently wrapping FLINT fq modules into new Sage classes for finite >> fiels and got strange coercion errors when running non trivial code. >> Indeed, the polynomial ring constructors use a dictionary a

[sage-devel] Re: cygwin64 build error for ppl-1.1

The ECL issue looks strange... The failed install should have left the build directory somewhere in Sage's tree (look under local/var/tmp/.../ecl-.../ or smtg like that). Can you cd there and check that ecl.exe is actually not present? (I'll try to give you more details later on the directory name

[sage-devel] Re: cygwin64 build error for ppl-1.1

As far as ATLAS is concerned, it's hellishly long and that's to be expected. You can try using a pretuned config by setting SAGE_ATLAS_ARCH=base/fast or using SAGE_ATLAS_LIB to use system-wide libraries as Dima suggested. I'll have a look at ECL issue tonight. -- You received this message becau

[sage-devel] Equality, hashing and polynomial rings

Hi, I'm currently wrapping FLINT fq modules into new Sage classes for finite fiels and got strange coercion errors when running non trivial code. Indeed, the polynomial ring constructors use a dictionary and so relies on the hash of finite fields (the parents). By some chance, the hashes of two

[sage-devel] Re: cygwin64 build error for ppl-1.1

If you want to attempt a build on Cygwin64 pleas follow http://trac.sagemath.org/wiki/Cygwin64Port and use the u/jpflori/cygwin64 branch on Sage's git. (Unless that's already what you are doing.) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. T

[sage-devel] Re: Curious problem with Sage "fat_binary" tarballs

SAGE_FAT_BINRAY is quite fragile. If you really want me to, I can break it on quite every system. Are the machine really different? Maybe its just a problem with R and can be fixed. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe fr

Re: [sage-devel] New IML release

More fun at http://trac.sagemath.org/ticket/16706. If nobody raises its voice, I'll just forward the current archive there to Arne for release. Best, JP On Wednesday, July 23, 2014 12:35:38 PM UTC+2, Jean-Pierre Flori wrote: > > > > On Wednesday, July 23, 2014 12:30:15 PM UTC+

Re: [sage-devel] New IML release

On Wednesday, July 23, 2014 12:30:15 PM UTC+2, François wrote: > > In that case the README. > Done, I've updated evrything. -- 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 a

<    1   2   3   4   5   6   7   8   9   >