Just to echo this sentiment a bit. I seem to recall reading somewhere that pickles are not intended to be long-term archives as there is no guarantee that a pickle made in one version of python would work in another version, much less between different versions of the same (or similar) packages.
Ben Root On Tue, Feb 25, 2014 at 3:39 AM, Pierre Haessig <pierre.haes...@crans.org>wrote: > Hi, > > Le 25/02/2014 09:19, Chris a écrit : > > I have some old code that uses cPickle.loads which used to work, but now > > reports an error in loading the module Numeric. Since Numeric has been > > replaced by numpy, this makes sense, but, how can I get cPickle.loads to > > work? I tested the code again on an older machine and it works fine > > there, but, I'd like to get it working again on a modern set-up as well. > > > > Thanks! > > > Do you have big archives of pickled arrays ? > > I have the feeling that your question is related to this SO question: > > http://stackoverflow.com/questions/2121874/python-pickling-after-changing-a-modules-directory > From the accepted SO answer, I'm getting that it is not easy to manually > edit the pickled files (except in the case of the ASCII pickle protocol) > > So if you still have an old setup that can open the pickled arrays, I > would suggest to use it to convert it to a format that is more > appropriate to long term archiving. Maybe a simple text format (CSV ?) > or HDF5 depending on the volume and the complexity (but I'm not a > specialist data archiving) > > best, > Pierre > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
