On 2012-02-01, at 2:53 AM, Gael Varoquaux wrote: > All your remarks are valid, but what it really boils down to is that general > purpose persistence is hard. Given well-defined objects, good persistence > scheme can be developped, but than you have to worry about transition that > code as the data models of the objects evolve. Hard again.
Yep, this is very true. That's the one area where I can't blame the developers: it's a design decision they had to make, and there really isn't a right answer. But the implementation issues (blowing the stack, messed up exception handling, excessive memory usage, etc.) seem to me to be problems with pickle itself rather than fundamental problems with serialization. The fact that it separates your code from your data (meaning code changes make unpickling break) but *still* manages to allow for arbitrary malicious code execution is particularly annoying, and seems to partially defeat the purpose of not serializing byte code. David ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
