This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ac.james
Recipients ac.james, georg.brandl
Date 2009-06-15.23:19:52
SpamBayes Score 1.9296911e-07
Marked as misclassified No
Message-id <1245107994.41.0.726587002709.issue6290@psf.upfronthosting.co.za>
In-reply-to
Content
When using cPickle to pickle / unpickle an object instance whose
__dict__ contains a dictionary of NumPy Arrays (on a windows32 system),
some of the array elements have the wrong type raising a ValueError:
could not convert string to float.  

On UNIX platform this error does not occur, and the data is read out in
the correct type every time.  
Forcing the caller to use pickle.py module instead removed the issue.

Statements about the imprecision of cPickle (such as issue1536, 655802),
or its deprecaition (now I can't find where that was mentioned), would
assist.  By contrast the current state of the documentation implies that
cPickle is better overall, and thus should be used preferentially.
History
Date User Action Args
2009-06-15 23:19:55ac.jamessetrecipients: + ac.james, georg.brandl
2009-06-15 23:19:54ac.jamessetmessageid: <1245107994.41.0.726587002709.issue6290@psf.upfronthosting.co.za>
2009-06-15 23:19:52ac.jameslinkissue6290 messages
2009-06-15 23:19:52ac.jamescreate