On Thu, Mar 26, 2009 at 8:50 AM, Jason Bandlow wrote:
>
> Hi all,
>
> When I start up a clean version of sage 3.4 on my local machine and
> enter the following into a notebook cell:
>
> M=load('http://www.math.upenn.edu/~jbandlow/sage_data/dic_of_kst_to_G_cob_mats.sobj')
> # This object is a dict
William Stein wrote:
> On Thu, Mar 26, 2009 at 8:50 AM, Jason Bandlow wrote:
>> Hi all,
>>
>> When I start up a clean version of sage 3.4 on my local machine and
>> enter the following into a notebook cell:
>>
>> M=load('http://www.math.upenn.edu/~jbandlow/sage_data/dic_of_kst_to_G_cob_mats.sobj'
On Sat, Mar 28, 2009 at 6:26 AM, Jason Bandlow wrote:
>> I'm guessing this is a subtle 32 versus 64-bit issue involving
>> pickling and assumptions made somewhere in the combinat or other sage
>> code involving 32/64-bit. The notebook is 64-bit and I bet your
>> computer is 32-bit.
>>
>> By the
On Mar 28, 8:59 am, William Stein wrote:
> I know of one place in sage where objects cache their hash for
> efficiency reasons (e.g., I think Sage matrices do). I hadn't thought
> about the fact that pickling, moving to an object to a platform where
> the hashes are different, and unpickling, wou