On Sat, Sep 4, 2010 at 7:33 PM, Jason Grout <jason-s...@creativetrax.com> wrote: > In improving fast_callable, I'm working on removing fast_float so we don't > have to maintain it. Of course, the pickle jar complains that, with the > fast_float code gone, a pickle in the pickle jar doesn't unpickle. > > So... > > 1. Do people care if we can't unpickle fast_float objects? (that would save > a lot of effort if it's not needed) > > 2. There seem to be two ways to unpickle fast_float objects: (a) keep the > old code around, or (b) convert them to fast_callable objects. (a) leads to > a bigger maintenance problem for us, while (b) leads to a (lot?) more > effort, and possibly slight incompatibilities. Any preference? >
I doubt there's a lot of fast_float pickled objects laying around, but it may be worth deprecating them before removing them entirely. Also, in case some pickle is holding on to a reference of a fast_float, it may make sense to always keep the objects around (e.g. they could unpickle into something that only raises exceptions when used) to prevent larger pickles from breaking. - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
