Hi all, I seem to have problems with pickling and i was wondering whether it is stackless related (i found a presentation by Anselm Kruis saying that stackless pickles modules).
I found two problems that seem odd to me: 1) if i pickle-save my model, remove a class from my modules and then load the save, sometimes the unpickler crashed even when the class is not used in my model (it still looks for the removed class, although i see no reason the unpickler needs it for the model i saved). 2) If i change a class after saving the model, and then load the model again, the loaded model seems to use a pre-change class definition. This means that during testing i need to recreate the model (which can be quite complex) after any changes to the classes it uses (and even after removing classes i don't use), even if the change should not influence the saved and reloaded pickle in any way. It also means that save files become much more brittle in any production version of the program. So my questions are, is this caused by stackless (compared to vanilla python) and if so, what triggers the pickling of modules and how can i influence that or use the vanilla version of pickle instead. Cheers, Lars -- ==================================== Lars van Gemerden [email protected] +31 6 26 88 55 39 ====================================
_______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
