Hi, On 2019-08-02, E. Madison Bray <erik.m.b...@gmail.com> wrote: > Sage's use of pickle for save()/load() is a mis-feature IMO. One that > made sense at a time, for lack of a better choice. And that's still > useful as a means of saving/restoring some objects between sessions. > But I don't think you can always guarantee it to be stable.
What better format do you suggest? I am surprised that you see a fundamental problem with Sage's pickling: If code or even the data structures change, then it is still possible to fit old data (pickles) into the new data format. Evidently, when you decide to change the data structures in your algorithms, you *have* to write a function that translates old data into the new format - but on the positive side, you *can* write such a function. Is there a different approach that allows to change your code over time (evidently that's absolutely needed for a project that isn't dead!) while still being able to read data that you have stored with your old code? Best regards, Simon -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/qi13nj%2425kk%241%40blaine.gmane.org.
