Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #5588 > unrolled thread

Re: cPickle -> invalid signature

Started byNeal Becker <ndbecker2@gmail.com>
First post2011-05-17 14:26 -0400
Last post2011-05-17 14:26 -0400
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: cPickle -> invalid signature Neal Becker <ndbecker2@gmail.com> - 2011-05-17 14:26 -0400

#5588 — Re: cPickle -> invalid signature

FromNeal Becker <ndbecker2@gmail.com>
Date2011-05-17 14:26 -0400
SubjectRe: cPickle -> invalid signature
Message-ID<mailman.1686.1305656830.9059.python-list@python.org>
Gabriel Genellina wrote:

> En Tue, 17 May 2011 08:41:41 -0300, Neal Becker <ndbecker2@gmail.com>
> escribió:
> 
>> What does it mean when cPickle.load says:
>> RuntimeError: invalid signature
>>
>> Is binary format not portable?
> 
> Are you sure that's the actual error message?
> I cannot find such message anywhere in the sources.
> The pickle format is quite portable, even cross-version. As a generic
> answer, make sure you open the file in binary mode, both when writing and
> reading.
> 

Yes, that's the message.

Part of what is pickled is a numpy array.  I am writing on a 32-bit linux system 
and reading on a 64-bit system.  Reading on the 64-bit system is no problem.

Maybe the message comes from numpy's unpickling?

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web