Re: [sage-devel] linbox 64-bit charpoly

On Tue, Sep 27, 2016 at 8:34 PM, 'Bill Hart' via sage-devel < sage-devel@googlegroups.com> wrote: > > > On Tuesday, 27 September 2016 20:53:28 UTC+2, Jonathan Bober wrote: >> >> On Tue, Sep 27, 2016 at 7:18 PM, 'Bill Hart' via sage-devel < >> sage-...@googlegroups.com> wrote: >> >>> I'm pretty

Re: [sage-devel] linbox 64-bit charpoly

On Tue, Sep 27, 2016 at 8:02 PM, William Stein wrote: > On Tue, Sep 27, 2016 at 11:53 AM, Jonathan Bober > wrote: > > On Tue, Sep 27, 2016 at 7:18 PM, 'Bill Hart' via sage-devel > > wrote: > >> > >> I'm pretty sure the charpoly

Re: [sage-devel] Re: memory management issue: deleted variables not released

I just noticed this thread because of your recent reply, and happened to read through. (I haven't regularly read sage-devel for a while.) As to your original email: I think there is a subtle python memory management issue there. If you run sage: BIG=myfunction(somevars) sage:

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

On Tue, Sep 27, 2016 at 2:10 PM, Volker Braun wrote: > I may have time next weekend to containerize the buildbot, though no > promises. It does need quite a lot of disk space (the old one was about 50GB > iirc) to hold all the build logs and binary builds. The new machine

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

I may have time next weekend to containerize the buildbot, though no promises. It does need quite a lot of disk space (the old one was about 50GB iirc) to hold all the build logs and binary builds. Whats the plan for external networking and secrets? On Tuesday, September 27, 2016 at 9:57:43

Re: [sage-devel] Re: memory management issue: deleted variables not released

Tried but it didn't work out. MathCloud admins say they can't help. Tried also at SageCell but the calculation wouldn't end either way after several hours. Any ideas? Denis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

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

On Tue, Sep 27, 2016 at 12:54 PM, Harald Schilly wrote: > On Tue, Sep 27, 2016 at 9:29 PM, Dima Pasechnik wrote: >>> we can't, because there are filesize limits. >> how about git-lfs ? (which is probably not cheap to use) > > I don't think we need any

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

On Tue, Sep 27, 2016 at 9:29 PM, Dima Pasechnik wrote: >> we can't, because there are filesize limits. > how about git-lfs ? (which is probably not cheap to use) I don't think we need any of that, a normal CDN is fine, too. Problem with using a commercial one is that the

Re: [sage-devel] linbox 64-bit charpoly

On Tuesday, 27 September 2016 20:53:28 UTC+2, Jonathan Bober wrote: > > On Tue, Sep 27, 2016 at 7:18 PM, 'Bill Hart' via sage-devel < > sage-...@googlegroups.com > wrote: > >> I'm pretty sure the charpoly routine in Flint is much more recent that 2 >> years. Are you referring to a Sage

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

On Tue, Sep 27, 2016 at 5:57 PM, Harald Schilly wrote: > On Tue, Sep 27, 2016 at 7:39 PM, William Stein wrote: >> no volunteers to migrate files/build/rsync.sagemath.org... We should >> just switch to GitHub. > > we can't, because there are filesize

Re: [sage-devel] linbox 64-bit charpoly

On Tue, Sep 27, 2016 at 11:53 AM, Jonathan Bober wrote: > On Tue, Sep 27, 2016 at 7:18 PM, 'Bill Hart' via sage-devel > wrote: >> >> I'm pretty sure the charpoly routine in Flint is much more recent that 2 >> years. Are you referring to a Sage

Re: [sage-devel] linbox 64-bit charpoly

On Tue, Sep 27, 2016 at 7:18 PM, 'Bill Hart' via sage-devel < sage-devel@googlegroups.com> wrote: > I'm pretty sure the charpoly routine in Flint is much more recent that 2 > years. Are you referring to a Sage implementation on top of Flint > arithmetic or something? > It is just a problem with

[sage-devel] Re: OS X testers needed

OS X 10.10.2 Yosemite: $ ./sage -tp --long src/sage/libs/pari -- All tests passed! -- Total time for all tests: 9.1 seconds cpu time: 14.0 seconds

Re: [sage-devel] linbox 64-bit charpoly

I'm pretty sure the charpoly routine in Flint is much more recent that 2 years. Are you referring to a Sage implementation on top of Flint arithmetic or something? The only timing that I can find right at the moment had us about 5x faster than Sage. It's not in a released version of Flint

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

On Tue, Sep 27, 2016 at 7:39 PM, William Stein wrote: > no volunteers to migrate files/build/rsync.sagemath.org... We should > just switch to GitHub. we can't, because there are filesize limits. -- h -- You received this message because you are subscribed to the Google

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

William Stein wrote: > On Mon, Sep 26, 2016 at 3:10 PM, William Stein wrote: >>> On Mon, Sep 26, 2016 at 6:22 AM, Volker Braun wrote: Yes, both the file server files.sagemath.org and buildbot build.sagemath.org are down... >> >> I've done

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

On Mon, Sep 26, 2016 at 3:10 PM, William Stein wrote: >> On Mon, Sep 26, 2016 at 6:22 AM, Volker Braun wrote: >>> Yes, both the file server files.sagemath.org and buildbot build.sagemath.org >>> are down... > > I've done what I can and right now > >-

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_ATLAS_LIB

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,