Re: [sage-devel] Re: Getting rid of the pickle jar

I agree that removing pickles from 6+ years ago is a good idea. I do think, however, that the idea of being able to save objects between versions of Sage is valuable. And we need some way to test it. Maybe we could move to some sort of rolling pickle jar, where we allow deprecations after a

Re: [sage-devel] Online Sage Days

Sorry for dropping the ball on organizing these. Based on the results of the survey, I'm going to propose Monday, November 6 starting at 4pm EST, 10pm CET. The first topic will be the Python 3 transition: what needs to be done and how we can get more people involved in the effort. If you'd like

[sage-devel] Re: Getting rid of the pickle jar

Hi Erik, On 2017-10-27, Erik Bray wrote: > Plus, while pickling has many valid runtime use-cases, particularly > for IPC, and short-term preservation of objects between interpreter > sessions, it was *never* intended for long-term data storage, Seriously? Said who? I

[sage-devel] Re: Getting rid of the pickle jar

The conventional wisdom is to avoid pickles in favour of JSON (the latter is a platform-independent human-parseable text, the former is some Python-only binary stuff). -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

[sage-devel] Re: Unable to build GAP3

> >> Sorry for the delayed response. I didn't have access to this particular >> machine over the weekend. >> >> I would try getting rid of "-static" in that call to gcc. >> >> >> I did that and now I get: >> >> gcc -o gap gap.o system.o gasman.o scanner.o idents.o read.o eval.o >> integer.o

[sage-devel] Re: Getting rid of the pickle jar

Thats still only addressing that objects can be unpickled; You'd also have to run the entire testsuite with the unpickled objets if you want to have any reasonable guarantee that they are actually working. Put differently, how likely do you think it is that some old pickle unpickles and passes

Re: [sage-devel] Re: Getting rid of the pickle jar

On Sun, Oct 29, 2017 at 7:58 AM Dima Pasechnik wrote: > The conventional wisdom is to avoid pickles in favour of JSON (the latter > is a platform-independent human-parseable text, the former is some > Python-only binary stuff). Whether this is a good idea depends a lot on

Re: [sage-devel] Re: Getting rid of the pickle jar

On Sun, Oct 29, 2017 at 12:46 PM Jeroen Demeyer wrote: > On 2017-10-29 20:22, Simon King wrote: > > As part of the release process of a new version of SageMath, > > a new version of the pickle jar is created by some patchbots > > on m different machines and replaces the m

[sage-devel] Some sparse matrices cleanup and question on parallelism

Hey all, I'm digging through the (sparse) matrix code right now as I have some ~67000 x 67000 square sparse matrices over QQ(q) (given as the fraction field of ZZ[q]) and the bottleneck in my computations are solving kernels (which isn't too bad, takes about half a day) and taking an

[sage-devel] Re: Getting rid of the pickle jar

On 2017-10-29, David Roe wrote: > I agree that removing pickles from 6+ years ago is a good idea. > > I do think, however, that the idea of being able to save objects between > versions of Sage is valuable. And we need some way to test it. Maybe we > could move to some sort

Re: [sage-devel] Re: Getting rid of the pickle jar

On 2017-10-29 20:22, Simon King wrote: As part of the release process of a new version of SageMath, a new version of the pickle jar is created by some patchbots on m different machines and replaces the m oldest versions of the pickle jar. That's the easy part. The hard part is deciding what to

[sage-devel] Re: Unable to build GAP3

Sorry for the delayed response. I didn't have access to this particular machine over the weekend. I would try getting rid of "-static" in that call to gcc. I did that and now I get: gcc -o gap gap.o system.o gasman.o scanner.o idents.o read.o eval.o integer .o rational.o cyclotom.o

Re: [sage-devel] Re: Getting rid of the pickle jar

On Monday, October 30, 2017 at 5:46:49 AM UTC+10, Jeroen Demeyer wrote: > > On 2017-10-29 20:22, Simon King wrote: > > As part of the release process of a new version of SageMath, > > a new version of the pickle jar is created by some patchbots > > on m different machines and replaces the m

Re: [sage-devel] Re: Getting rid of the pickle jar

I think tying it in with TestSuite(foo).run() is a good idea, but we probably don't want to store pickles for every one (since test suites can be run for multiple elements of the same type). Maybe check to see if a pickle has already been created for a given class, and if not, create one? David

[sage-devel] Re: Unable to build GAP3

On Sunday, October 29, 2017 at 11:42:41 PM UTC, Travis Scrimshaw wrote: > > > Sorry for the delayed response. I didn't have access to this particular > machine over the weekend. > > I would try getting rid of "-static" in that call to gcc. > > > I did that and now I get: > > gcc -o gap gap.o