On Mon, Oct 30, 2017 at 4:33 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2017-10-30 16:28, William Stein wrote: >> >> Not necessarily. Pickle is *the* canonical extensible object >> serialization system for Python. It’s of course very extensible in >> that users can define how objects pickle, eg by defining a dunder reduce >> method. As such they can of course make that method store output in any >> binary format they want. > > > The question is not what is possible, but what is the recommended way of > doing things. Are we supposed to make our pickles hardware-independent or is > that hopeless anyway?
I guess it depends on what you mean by "supposed to". I believe that the pickle formats for built-in types are hardware-independent. E.g. int values are stored as little-endian and loaded as little-endian in a hardware-independent manner. So that at least appears to be the intent. But I don't know if there's any *requirement* that a pickle be hardware-independent when it comes to custom types, though in general it's probably better that they are. But for custom code that, say, targets only one hardware platform anyways then that's up to the developer.... -- 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, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
