On Friday, January 17, 2014 5:32:48 PM UTC-5, Nils Bruin wrote:
>
> si4 = unpickle_newobj(pg_Partition_class, ())
> unpickle_build(si4, {'_hash':11648069979105038r, '_list':[]})
>
Which is pretty much the reason why pickles are a bad archival format.
Anything sufficiently complicated will depend
Hi Nils,
On 2014-01-17, Nils Bruin wrote:
> It looks like it's putting a cache dictionary on the Partition_class object
> that has a hash value in it! That means that whenever the implementation of
> the hash on Partition changes, these pickles would be dangerously
> out-of-date. This is proba
Oh boy, the pickle as it is is always going to be horribly broken anyway:
si4 = unpickle_newobj(pg_Partition_class, ())
unpickle_build(si4, {'_hash':11648069979105038r, '_list':[]})
It looks like it's putting a cache dictionary on the Partition_class object
that has a hash value in it! That mean
On 1/17/14 2:05 PM, Nils Bruin wrote:
> On Sunday, January 12, 2014 11:01:50 PM UTC-8, Anne Schilling wrote:
>
> I agree with Travis that we should just remove the jar, given that the
> old k-Schurs were deprecated for over a year!
>
>
> The period of deprecation is actually irrelevant for
On Sunday, January 12, 2014 11:01:50 PM UTC-8, Anne Schilling wrote:
>
> I agree with Travis that we should just remove the jar, given that the old
> k-Schurs were deprecated for over a year!
>
The period of deprecation is actually irrelevant for whether a pickle
should be unpickleable. The rele
This was broken in sage-5.10. It works of sage-5.9.
--
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,
You are certainly right, and I agree that Ctrl-C would be simpler.
John
On 17 January 2014 18:25, Simon King wrote:
> Hi John,
>
> On 2014-01-17, John Cremona wrote:
>>> This works for me as well. The problem only occurs when typing a new
>>> definition, not when I go back to an old one.
>>>
>>
Hi Andrew,
On 2014-01-17, Andrew wrote:
>> Or do you suggest to "update the pickle jar" in the sense of "remove old
>> pickles and *replace* them by new ones"?
>>
>
> I was mainly thinking of adding new pickles rather than removing old ones.
OK, then we agree here.
> My main point is that at
Hi John,
On 2014-01-17, John Cremona wrote:
>> This works for me as well. The problem only occurs when typing a new
>> definition, not when I go back to an old one.
>>
>
> Agreed. But when in the middle of the new definition you can type an
> up-arrow to chenge previous lines? I can even go bac
On Jan 17, 2014 10:10 AM, "Andrew" wrote:
>
>
>
> On Friday, 17 January 2014 15:07:26 UTC+1, Nathann Cohen wrote:
>>
>>
>> Well. Don't we keep old versions of Sage too ? The guy can save his data
by reinstalling the version he used just before updating his Sage install.
Even Sage 2.0 if he feels l
On Friday, January 17, 2014 7:14:58 AM UTC-8, Nathann Cohen wrote:
>
> Well, that's what would happen if 2.0 was the latest version able to
> open those pickles, and that the guy never updated his version of Sage
> until today.
That's not how bitrot tends to work. The more likely scenario is th
Well we already have virtual machines, we just need to archive them ;-)
On Friday, January 17, 2014 10:53:54 AM UTC-5, Dan Drake wrote:
>
> Then the problem is turned into the problem of getting the VM to run. My
> impression is that the file format for VM images is pretty stable, so
> this wou
On Fri, 17 Jan 2014 at 07:10AM -0800, Andrew wrote:
> Well, in principle yes, but how easy do you think it will be to
> compile sage 2.0 in 2020? My guess is that this will be more difficult
> than writing new code to read old pickles -- should any of them no
> longer be supported:)
This is relate
> Well, in principle yes, but how easy do you think it will be to compile sage
> 2.0 in 2020? My guess is that this will be more difficult than writing new
> code to read old pickles -- should any of them no longer be supported:)
Well, that's what would happen if 2.0 was the latest version able to
On Friday, 17 January 2014 14:53:22 UTC+1, Simon King wrote:
>
> Hi Andrew,
>
> On 2014-01-17, Andrew > wrote:
>
> Do you suggest to "update the pickle jar" in the sense of "whenever
> someone implements a new data structure or changes an existing data
> structure, then an example of the new/
On Friday, 17 January 2014 15:07:26 UTC+1, Nathann Cohen wrote:
>
>
> Well. Don't we keep old versions of Sage too ? The guy can save his data
> by reinstalling the version he used just before updating his Sage install.
> Even Sage 2.0 if he feels like it.
>
> Well, in principle yes, but how ea
On 17 January 2014 13:41, Simon King wrote:
> Hi John,
>
> On 2014-01-17, John Cremona wrote:
Holding down
the Backspace key?
>>>
>>> Nope, since it will only bring you to the beggining of the line, which
>>> won't help in a multiline command.
>>
>> That's funny -- in my terminal that
>
> But I think it is absolutely not acceptable to say: "OK, let's remove
> the pickle jar and keep going until some angry user tells us that his
> seminal 2008 work that took him 10 months of computation time can not
> be accessed with the latest version of Sage."
Well. Don't we keep old ve
Hi Andrew,
On 2014-01-17, Andrew wrote:
> I would like to suggest that we either:
>
>1. Maintain the pickle jar properly, by which I mean that the jar is
>updated regularly (and probably tracked by git).
>2. Remove the pickle jar entirely.
>
> In principle, having a pickle jar is a g
Hi John,
On 2014-01-17, John Cremona wrote:
>>> Holding down
>>> the Backspace key?
>>
>> Nope, since it will only bring you to the beggining of the line, which
>> won't help in a multiline command.
>
> That's funny -- in my terminal that does work.
In my case (openSuse), I can go back until th
On 17 January 2014 12:18, Simon King wrote:
> Hi John,
>
> On 2014-01-17, John Cremona wrote:
>> Press return after making sure there's a syntax error?
>
> OK, that seems to work:
>
> sage: def foo(x):
> : print typo(x)
> : arrg!
> :
> File "", line 3
> arrg!
> ^
> S
Hi John,
On 2014-01-17, John Cremona wrote:
> Press return after making sure there's a syntax error?
OK, that seems to work:
sage: def foo(x):
: print typo(x)
: arrg!
:
File "", line 3
arrg!
^
SyntaxError: invalid syntax
> Holding down
> the Backspace key?
Nope
On Fri, Jan 17, 2014 at 2:35 AM, Andrew wrote:
> I'd be interested in knowing how many people actually use/store pickles and
> whether this is enough to justify maintaining the pickle jar. Speaking for
> myself, I never use pickles and the only time that I have ever looked at
> them is when I was
I'd be interested in knowing how many people actually use/store pickles and
whether this is enough to justify maintaining the pickle jar. Speaking for
myself, I never use pickles and the only time that I have ever looked at
them is when I was upgrading various classes and this broke some of the
On 17 January 2014 08:18, Simon King wrote:
> On 2014-01-17, P Purkayastha wrote:
>> Here is a weird bug in the sage command line. As you may have noticed,
>> the sage: prompt does not return, and the command is actually still
>> inside the for loop.
>
> Yes, that's annoying. When typing a multil
On Friday, January 17, 2014 8:32:20 AM UTC+1, Jeroen Demeyer wrote:
>
> On 2014-01-16 01:51, ref...@uncg.edu wrote:
> > Before I begin, I'd like to thank you in advance for any help I get with
> > this question. I'm currently working with some heavy computation and
> > decided to cython-ize
On 2014-01-17, P Purkayastha wrote:
> Here is a weird bug in the sage command line. As you may have noticed,
> the sage: prompt does not return, and the command is actually still
> inside the for loop.
Yes, that's annoying. When typing a multiline command, I used to hit
Ctrl-C if I noticed a ty
27 matches
Mail list logo
