Re: [sage-release] Sage 8.5.beta4 released

er 1st is feature freeze > Jan 1st ist release target > > > On Tuesday, November 20, 2018 at 5:55:56 PM UTC+1, Erik Bray wrote: >> >> I might have missed it, but have you ever mentioned if there is a >> target release date and/or cutoff date for non-critical issues for >

Re: [sage-release] Sage 8.5.beta4 released

I might have missed it, but have you ever mentioned if there is a target release date and/or cutoff date for non-critical issues for this version? On Sun, Nov 18, 2018 at 9:30 PM Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git branch. >

Re: [sage-release] square root very strange in 8.5.beta3

On Thu, Nov 15, 2018 at 8:39 AM Emmanuel Charpentier wrote: > > > > Le mercredi 14 novembre 2018 12:29:36 UTC+1, Erik Bray a écrit : > >> >> However, one thing I do find surprising about the global sqrt >> function, which is different from some other global

Re: [sage-release] square root very strange in 8.5.beta3

On Wed, Nov 14, 2018 at 10:32 AM Bruno Grenet wrote: > > As far as I can tell, this behavior is not new. The (default) choice > made for the square root of an integer is to return an exact answer > rather than an approximation. Thus sqrt(9) = 3, sqrt(10) = sqrt(10) and > sqrt(12) = 2*sqrt(3). On

Re: [sage-release] Re: Sage 8.5.beta3 released

On Mon, Nov 12, 2018 at 10:51 AM Eric Gourgoulhon wrote: > > Le lundi 12 novembre 2018 08:45:59 UTC+1, fchap...@gmail.com a écrit : >> >> This seems to break almost all the patchbots. Problem building the sagenb >> doc, probably. > > > Confirmed: incremental build from Sage 8.5.beta2 yields: > >

Re: [sage-release] Sage 8.5.beta1 released

Any thoughts on the release schedule, such that it is? I thought having the rough October 1st guideline for the last release to be helpful. Although we ended up cutting off changes a little later than that (and it would have been nice to have an updated projection as the October 1st date came

Re: [sage-release] Re: Sage 8.4.rc0 released

On Mon, Oct 8, 2018 at 7:53 AM Jeroen Demeyer wrote: > > On 2018-10-07 21:32, Volker Braun wrote: > > I've seen this sometimes when running out of memory (docbuild gets stuck > > instead of erroring out) > > This is just general suckiness of multiprocessing.Pool > > I have a long-standing plan to

Re: [sage-release] Sage 8.4.beta6 released

On Sat, Sep 22, 2018 at 12:36 PM Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git branch. > Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > > b84538eeea (tag: 8.4.beta6, trac/develop) Updated

Re: [sage-release] Sage 8.4.beta5 released

On Mon, Sep 17, 2018 at 10:05 AM Eric Gourgoulhon wrote: > > Le lundi 17 septembre 2018 09:10:19 UTC+2, Daniel Krenn a écrit : >> >> On 2018-09-15 15:25, Volker Braun wrote: >> > As always, you can get the latest beta version from the "develop" git >> > branch. Alternatively, the self-contained

Re: [sage-release] Sage 8.4.beta5 released

On Mon, Sep 17, 2018 at 5:04 AM Andy Howell wrote: > > Steven, > > Thanks for confirming I'm an idiot:) I did have a test.py in there. Sorry for > the noise. Re-running the tests to make sure, but its almost certainly my > fault. In fairness, that test is poorly written if merely having a file

Re: [sage-release] Sage 8.4.beta4 released

On Tue, Sep 11, 2018 at 2:56 PM Jeroen Demeyer wrote: > > On 2018-09-11 12:29, Erik Bray wrote: > > It's not very important. > > It's not very important for Sage. That's what I mean. If I can just turn it off in Sage that would be best. -- You received this message because

Re: [sage-release] Sage 8.4.beta4 released

On Tue, Sep 11, 2018 at 11:34 AM Erik Bray wrote: > > On Tue, Sep 11, 2018 at 11:08 AM Erik Bray wrote: > > > > On Fri, Sep 7, 2018 at 1:24 AM Volker Braun wrote: > > > > > > As always, you can get the latest beta version from the "develop" git &

Re: [sage-release] Sage 8.4.beta4 released

On Tue, Sep 11, 2018 at 11:51 AM Jeroen Demeyer wrote: > > On 2018-09-11 11:08, Erik Bray wrote: > > On Cygwin `make ptestlong` with 4 processes gave me a few random > > failures. I have a lot of browser tabs open so I'm getting a lot of > > spurious > > >

Re: [sage-release] Sage 8.4.beta4 released

On Tue, Sep 11, 2018 at 11:08 AM Erik Bray wrote: > > On Fri, Sep 7, 2018 at 1:24 AM Volker Braun wrote: > > > > As always, you can get the latest beta version from the "develop" git > > branch. Alternatively, the self-contained source tarball is at &g

Re: [sage-release] Re: Sage 8.4.beta3 released

`make ptestlong` still passing without a hitch on Cygwin. Thanks for the update! On Mon, Sep 3, 2018 at 2:01 PM Eric Gourgoulhon wrote: > > On Ubuntu 18.04 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + pull > develop, parallel (-j16) build OK and all tests passed (from make ptestlong). > >

Re: [sage-release] Sage 8.4.beta2 released

On Tue, Aug 28, 2018 at 1:57 PM Erik Bray wrote: > > On Tue, Aug 28, 2018 at 12:10 PM Jeroen Demeyer wrote: > > > > On 2018-08-28 11:34, Erik Bray wrote: > > > I did get one strange failure I have never seen before: > > > > > > sage -t --long --wa

Re: [sage-release] Sage 8.4.beta2 released

On Tue, Aug 28, 2018 at 12:10 PM Jeroen Demeyer wrote: > > On 2018-08-28 11:34, Erik Bray wrote: > > I did get one strange failure I have never seen before: > > > > sage -t --long --warn-long 304.2 src/sag

Re: [sage-release] Sage 8.4.beta2 released

Thanks for the beta--the inclusion of #25907 made a big difference for running the test suite on Cygwin--many fewer errors caused by running out of memory while running the tests :) I did get one strange failure I have never seen before: sage -t --long --warn-long 304.2

Re: [sage-release] Sage 8.4.beta1 released

On Thu, Aug 16, 2018 at 12:03 AM Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git branch. > Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > > 23a2b10da6 (tag: 8.4.beta1) Updated SageMath

Re: [sage-release] Re: Sage 8.3 released

On Thu, Aug 9, 2018 at 4:48 PM Harald Schilly wrote: > > > > On Friday, August 3, 2018 at 1:47:49 PM UTC+2, Volker Braun wrote: >> >> The "master" git branch has been updated to Sage-8.3. As always, you can get >> the latest beta version from the "develop" git branch. Alternatively, the >>

Re: [sage-release] Sage 8.4.beta0 released

On Tue, Aug 7, 2018 at 10:41 AM Erik Bray wrote: > > On Mon, Aug 6, 2018 at 5:47 PM Erik Bray wrote: > > > > On Sun, Aug 5, 2018 at 12:34 PM Volker Braun wrote: > > > > > > As always, you can get the latest beta version from the "develop" git &

Re: [sage-release] Sage 8.4.beta0 released

On Mon, Aug 6, 2018 at 5:47 PM Erik Bray wrote: > > On Sun, Aug 5, 2018 at 12:34 PM Volker Braun wrote: > > > > As always, you can get the latest beta version from the "develop" git > > branch. Alternatively, the self-contained source tarball is at &g

Re: [sage-release] Sage 8.4.beta0 released

On Sun, Aug 5, 2018 at 12:34 PM Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git branch. > Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html Ubuntu 14.04, make ptestlong, all tests passed! -- You

Re: [sage-release] Re: Sage 8.3.beta1 released

On Wed, May 16, 2018 at 9:56 AM, John Cremona wrote: > I started to build this yesterday after pulling from trac into a place where > beta0 had already built OK. This morning I find the lines > > [scipy-0.19.1] Skipping scipy as it is not installed. > [scipy-0.19.1]

Re: [sage-release] Re: Sage 8.3.beta1 released

Thanks for the release. On Ubuntu 14.04 I get LOTS of test timeouts that I didn't get previously. It's possible though that the system is just uder heavy load, but even re-running the tests with --failed keeps giving me timeouts for some modules. So I'm concerned about a real performance

Re: [sage-release] Re: Release process

On Tue, May 15, 2018 at 3:11 PM, Jeroen Demeyer <j.deme...@ugent.be> wrote: > On 2018-05-15 14:35, Erik Bray wrote: >> >> I'm not convinced that's a real problem. This is what I meant by "yes >> its contents may change and shift rapidly, but for a sophisticated >

Re: [sage-release] Re: Release process

On Sat, May 12, 2018 at 10:31 AM, Marc Mezzarobba wrote: > Jeroen Demeyer wrote: >> To be honest, I think it's not very meaningful to do that without >> consulting the release manager. I mean, you can write up all the >> documentation that you want; in the end, it's the

Re: [sage-release] Release process

On Mon, May 7, 2018 at 4:55 PM, Jeroen Demeyer <j.deme...@ugent.be> wrote: > (starting a new thread for the discussion about the current very slow pace > of merging tickets) > > On 2018-05-07 16:28, Erik Bray wrote: >> >> If it's not clear, shall I write up some more

Re: [sage-release] Re: Sage 8.2.rc4 released

On Sat, May 5, 2018 at 10:21 PM, <nbr...@sfu.ca> wrote: > On Thursday, April 26, 2018 at 7:11:52 AM UTC-7, Erik Bray wrote: >> >> >> Given such a branch to work in, it becomes less "urgent" to finish a >> release since it no longer needs to block nor

Re: [sage-release] Re: Sage 8.2.rc4 released

On Thu, Apr 26, 2018 at 3:55 PM, Jeroen Demeyer <j.deme...@ugent.be> wrote: > On 2018-04-26 12:29, Erik Bray wrote: >> >> But I'm told that's somehow impossible for Sage. > > > I don't think that it's fundamentally impossible. But it would require > changes to

Re: [sage-release] Sage 8.2.rc3 released

Thanks for getting the other two Cygwin issues fixed! It looks good to me. However, there is still a problem https://trac.sagemath.org/ticket/25150 still needs to be fixed--I'd be perfectly open to a different solution if the one I've suggested is bad. On Tue, Apr 17, 2018 at 12:34 AM, Volker

Re: [sage-release] Re: Sage 8.2.rc2 released

On Thu, Apr 12, 2018 at 11:09 AM, Erik Bray <erik.m.b...@gmail.com> wrote: > On Wed, Apr 11, 2018 at 6:59 PM, Eric Gourgoulhon > <egourgoul...@gmail.com> wrote: >> On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + >> pull develop, parallel (-j1

Re: [sage-release] Re: Sage 8.2.rc2 released

On Wed, Apr 11, 2018 at 6:59 PM, Eric Gourgoulhon wrote: > On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + > pull develop, parallel (-j16) build OK and make ptestlong passed except for > a single transient error to due to "Jmol failed to create

Re: [sage-release] Re: Sage 8.2.rc1 released

On Tue, Apr 10, 2018 at 10:45 AM, Erik Bray <erik.m.b...@gmail.com> wrote: > On Tue, Apr 3, 2018 at 10:56 AM, Eric Gourgoulhon > <egourgoul...@gmail.com> wrote: >> On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone, >> parallel (-j16) build OK an

Re: [sage-release] Re: Sage 8.2.rc1 released

On Tue, Apr 3, 2018 at 10:56 AM, Eric Gourgoulhon wrote: > On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone, > parallel (-j16) build OK and make ptestlong reported some transient errors > due to "Jmol failed to create file" in 4 files + a new

Re: [sage-release] Re: Sage 8.2.rc1 released

On Mon, Apr 2, 2018 at 11:09 AM, Eric Gourgoulhon wrote: > Since we have entered the 8.2.rc cycle, may I ask about the status of the > (blocker) ticket #24484 (broken export of Jupyter notebooks to any format) > ? > Without it, many users might complain (it was working

Re: [sage-release] Re: Sage 8.2.rc0 released

On Thu, Mar 29, 2018 at 3:20 PM, Eric Gourgoulhon wrote: > > > Le jeudi 29 mars 2018 14:16:22 UTC+2, Dima Pasechnik a écrit : >> >> >> >> On Thursday, March 29, 2018 at 12:31:15 PM UTC+1, Eric Gourgoulhon wrote: >>> >>> Hi, >>> >>> If one performs >>> git clone

Re: [sage-release] Re: Sage 8.2.beta8 released

On Thu, Mar 15, 2018 at 7:26 AM, Jeroen Demeyer <j.deme...@ugent.be> wrote: > On 2018-03-14 19:02, Erik Bray wrote: >> >> two Integers' mpz_t structs' _mp_d >> member (the array of limbs) is being set to the same memory address. > > > You really mean two dif

Re: [sage-release] Re: Sage 8.2.beta8 released

nfused as to why Sage was telling me I had a field with one element. > On 14/03/2018 16:49, Erik Bray wrote: >> >> I am now pretty consistently getting the following failure on Cygwin >> with 8.2beta8 (although strangely I've run the test once or twice with >> success t

Re: [sage-release] Re: Sage 8.2.beta8 released

On Wed, Mar 14, 2018 at 8:33 PM, Jeroen Demeyer <j.deme...@ugent.be> wrote: > On 2018-03-14 19:02, Erik Bray wrote: >> >> I see now--less likely a bug with MPIR/GMP itself, and more likely a >> bug with Sage's fast_tp_new stuff for Integer. > > > I don

Re: [sage-release] Re: Sage 8.2.beta8 released

On Wed, Mar 14, 2018 at 6:41 PM, Erik Bray <erik.m.b...@gmail.com> wrote: > On Wed, Mar 14, 2018 at 4:49 PM, Erik Bray <erik.m.b...@gmail.com> wrote: >> I am now pretty consistently getting the following failure on Cygwin >> with 8.2beta8 (although strangely I've

Re: [sage-release] Re: Sage 8.2.beta8 released

On Wed, Mar 14, 2018 at 4:49 PM, Erik Bray <erik.m.b...@gmail.com> wrote: > I am now pretty consistently getting the following failure on Cygwin > with 8.2beta8 (although strangely I've run the test once or twice with > success too...): > > sage -t --warn-long 164

Re: [sage-release] Re: Sage 8.2.beta8 released

I am now pretty consistently getting the following failure on Cygwin with 8.2beta8 (although strangely I've run the test once or twice with success too...): sage -t --warn-long 164.8 src/sage/structure/coerce_actions.pyx ** File

Re: [sage-release] Re: Sage 8.2.beta7 released

On Fri, Mar 9, 2018 at 9:53 AM, Emmanuel Charpentier wrote: > FWIW, (serially) builds successfully on Cygwin64 running on top of Windows 7 > (on Core i5 + 8 GB RAM), but only after applying Trac#24860. Serial build > needs about 15 hours. Tests will have to be run

Re: [sage-release] Re: Sage 8.2.beta6 released

On Mon, Feb 19, 2018 at 2:31 PM, Emmanuel Charpentier wrote: > On Debian testing running on core i5 + 8 GB RAM, 8.2.beta6 builds and passes > ptestlong with one (permanent) failure related to fricas (optional package) > : > > charpent@p-202-021:/usr/local/sage-8$

Re: [sage-release] Sage 8.2.beta4 released

On Wed, Jan 31, 2018 at 3:02 PM, Erik Bray <erik.m.b...@gmail.com> wrote: > On Tue, Jan 30, 2018 at 7:05 PM, François Bissey <frp.bis...@gmail.com> wrote: >> David Coudert got that (on sage-devel I think). Turns out the libpng >> install was broken for some reaso

Re: [sage-release] Sage 8.2.beta4 released

porting this which > makes it suspicious. Is something out there deleting libpng.so? I just did a full `make distclean && make build` and that seemed to fix it as well. I didn't try `./sage -f libpng` but I should have--that might have been faster :) I'll look into it. Thanks, E >

Re: [sage-release] Sage 8.2.beta4 released

On Sun, Jan 28, 2018 at 8:17 AM, Ralf Stephan wrote: > This is https://trac.sagemath.org/ticket/24599 > I'm trying now with the system gcc. I don't have this problem on Ubuntu but I am getting: [giac-1.4.9.45] libtool: link: g++ -g -O2 -fno-strict-aliasing

Re: [sage-release] Re: Sage 8.2.beta3 released

On Sun, Jan 21, 2018 at 11:48 AM, Emmanuel Charpentier wrote: > On Cygwin64 running on Windows 7 (without admin rights) on the very same > hardware as the previous report, a *serial* build of sage succeeds and > passes testlong (*not* ptestlong) with one failure,

Re: [sage-release] Sage 8.2.beta3 released

On Thu, Jan 18, 2018 at 1:01 AM, Volker Braun wrote: > After reinstalling the OSX buildslave from scratch since the OSX 10.13 > upgrade resulted in a bootloop (why not let your customers beta-test the > online migration to the new file system), we finally have a new release

Re: [sage-release] Sage 8.2.beta0 released

On Thu, Dec 14, 2017 at 11:36 AM, Dima Pasechnik wrote: > > > On Thursday, December 14, 2017 at 9:53:11 AM UTC, François Bissey wrote: >> >> I am sure I could get it directly from trac. It is just more convenient >> from github when you started with a clone from the github

Re: [sage-release] Re: Sage 8.1 released

On Mon, Dec 11, 2017 at 10:54 AM, wrote: > Volker, could you please get rid of the 66 "positive-reviewed as invalid" > tickets ? > > Frédéric > >

Re: [sage-release] Re: Sage 8.1.rc4 released

On Tue, Dec 5, 2017 at 6:16 PM, Emmanuel Charpentier wrote: > > > Le mardi 5 décembre 2017 18:03:19 UTC+1, Dima Pasechnik a écrit : >> >> The skylake wait was due to a bunch of active Sage users and devs needing >> it and asking for it. >> >> Perhaps we should aim

Re: [sage-release] Re: Sage 8.1.rc4 released

On Tue, Dec 5, 2017 at 6:05 PM, Emmanuel Charpentier wrote: > > > Le mardi 5 décembre 2017 10:52:14 UTC+1, Jeroen Demeyer a écrit : >> >> On 2017-12-04 19:18, Emmanuel Charpentier wrote: >> > I already reported >> >

Re: [sage-release] Re: Sage 8.1.rc4 released

On Tue, Dec 5, 2017 at 10:52 AM, Jeroen Demeyer wrote: > On 2017-12-04 19:18, Emmanuel Charpentier wrote: >> >> I already reported >> >> (twice >>

Re: [sage-release] Re: Sage 8.1.rc4 released

On Tue, Dec 5, 2017 at 10:52 AM, Jeroen Demeyer wrote: > On 2017-12-04 19:18, Emmanuel Charpentier wrote: >> >> I already reported >> >> (twice >>

Re: [sage-release] Re: Sage 8.1.rc4 released

On Mon, Dec 4, 2017 at 10:49 PM, Nicolas M. Thiery wrote: > On Sat, Dec 02, 2017 at 08:04:50AM -0800, Volker Braun wrote: >> Unfortunately, Eric's happiness will have to wait for 8.2.beta like >> all the other tickets ;-) > > It's not so much about Erik's happiness than

Re: [sage-release] Re: Sage 8.1.rc4 released

On Mon, Dec 4, 2017 at 3:16 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2017-12-04 14:35, Erik Bray wrote: >> >> I don't see why. What's the harm in merging a couple working branches? > > > The first rc version of Sage 8.1 is now almost 1 month

Re: [sage-release] Re: Sage 8.1.rc4 released

On Sat, Dec 2, 2017 at 5:04 PM, Volker Braun wrote: > On Saturday, December 2, 2017 at 1:54:02 PM UTC+1, tsc...@ucdavis.edu wrote: >> >> What about https://trac.sagemath.org/ticket/24297? I don't know if this >> problem materializes on other platforms, but I know Erik will

Re: [sage-release] Sage 8.1.rc2 released

On Fri, Nov 17, 2017 at 2:29 PM, Volker Braun wrote: > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > 92f95cef93 (tag: 8.1.rc2) Updated

Re: [sage-release] Sage 8.1.beta8 released

On Wed, Oct 18, 2017 at 5:29 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2017-10-18 16:57, Erik Bray wrote: >> >> Any ideas? Looks odd... > > > Please try again with attached patch Thanks, but no need--I think I see the issue. If you happ

Re: [sage-release] Sage 8.1.beta8 released

On Wed, Oct 18, 2017 at 4:59 PM, Jeroen Demeyer wrote: > Just to be clear: is this the *only* failure or are you seeing several > similar failures (if so: please show them all). (Assuming you're replying to me) No, just the one. -- You received this message because you

Re: [sage-release] Re: Sage 8.1.beta7 released

On Fri, Oct 13, 2017 at 9:38 AM, Sébastien Labbé wrote: > On a recent dell machine running Ubuntu 16.06, I get one failing test during > make ptestlong. The test pass when run alone : > > > sage -t --long src/sage/libs/gap/assigned_names.py >

Re: [sage-release] Sage 8.1.beta4 released

On Tue, Sep 5, 2017 at 8:37 PM, Volker Braun wrote: > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html On Windows I'm getting a bunch of

Re: [sage-release] Re: Sage 8.1.beta3 released

On Wed, Aug 23, 2017 at 10:44 AM, Emmanuel Charpentier wrote: > On Debian testing running on Core i7 + 16 GB RAM (MAKE="make -j8"), passes > ptestlong with one failure : > > -- > sage -t --long

Re: [sage-release] Sage 8.0.rc1 released

On Thu, Jul 6, 2017 at 12:52 AM, Volker Braun wrote: > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > c522ced Updated SageMath version

Re: [sage-release] Sage 8.0.rc0 released

Any chance someone can give me review on the following tickets: https://trac.sagemath.org/ticket/21233 https://trac.sagemath.org/ticket/23097 ? The first fixes the one consistently failing test on Cygwin. Florent reviewed it once a long time ago and had some comments, but I believe I've

Re: [sage-release] Sage 8.0.beta8 released

On Wed, May 24, 2017 at 11:49 PM, Volker Braun wrote: > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html LGTM on Cygwin, modulo

Re: [sage-release] Sage 8.0.beta6 released

On Mon, May 15, 2017 at 1:46 PM, Erik Bray <erik.m.b...@gmail.com> wrote: > Looks good on Cygwin, with patches for the few remaining blockers [1] > applied on top. Actually, now I'm having a problem with the sage/libs/ecl.pyx tests, which strangely did not have any problems on my o

Re: [sage-release] Sage 8.0.beta6 released

Looks good on Cygwin, with patches for the few remaining blockers [1] applied on top. Thanks, Erik [1] https://trac.sagemath.org/query?priority=blocker=needs_info=needs_review=needs_work=new=positive_review=porting%3A+Cygwin=id=summary=component=priority=status=type=milestone=priority On Sat,

Re: [sage-release] Re: Sage 8.0.beta5 released

Builds ok on Cygwin plus my additional patches for as yet unresolved tickets. Test results pending. On Fri, May 5, 2017 at 12:40 PM, Henri Girard wrote: > ubuntu xenial ok > > > Le 05/05/2017 à 12:06, Emmanuel Charpentier a écrit : > > On Debian testing running on Core

Re: [sage-release] Sage 7.6 released

On Sat, Mar 25, 2017 at 4:11 PM, Volker Braun wrote: > The "master" git branch has been updated to Sage-7.6. As always, you can get > the latest beta version from the "develop" git branch. Alternatively, the > self-contained source tarball is at >

Re: [sage-release] Re: Why is gcc built?

On Fri, Feb 24, 2017 at 7:06 PM, William Stein <wst...@gmail.com> wrote: > On Fri, Feb 24, 2017 at 4:31 AM, Erik Bray <erik.m.b...@gmail.com> wrote: > >> I don't particularly care what the default is but the point here in >> the first place is that it shouldn't tr

Re: [sage-release] Re: Why is gcc built?

On Fri, Feb 24, 2017 at 10:49 AM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2017-02-24 10:31, Erik Bray wrote: >> >> On Thu, Feb 23, 2017 at 5:26 PM, Dima Pasechnik <dimp...@gmail.com> wrote: >>> >>> one can still have something li

Re: [sage-release] Re: Why is gcc built?

On Thu, Feb 23, 2017 at 5:26 PM, Dima Pasechnik wrote: > one can still have something like: > --with-everything # build everything > --with-everythingneeded # build missing > etc... > to encode the most usual cases. Yes, I think this goes without saying. -- You received

Re: [sage-release] Re: Why is gcc built?

On Wed, Feb 22, 2017 at 5:13 PM, Simon King wrote: > PS: > > On 2017-02-22, Simon King wrote: >> Aha. Although I did "apt-get install gcc-fortran", gfortran is not there. > > And the reason is that apparently I didn't read the development manual >

Re: [sage-release] Sage 7.5.beta5 released

On Fri, Dec 2, 2016 at 2:06 AM, François Bissey wrote: > Can please people stop using files in SAGE_SRC at runtime and people > stop reviewing such things positively unless there is absolutely no > choices. > > In sage/plot/plot3d/base.pyx we have line 410 and