SpamBayes has, in storage.py, some code for storing pickles safely, but that code is only used for the training database and not the numerous other pickles used in SpamBayes, e.g. for caches. The result was that, when I was doing server-side filtering, cache pickles would be read while being written, and SpamBayes wasn't prepared to deal with the corruption.
I submitted a patch at http://sourceforge.net/tracker/index.php?func=detail&aid=1816240&group_id=61702&atid=498103 that factors that code out and uses it wherever pickles are saved. Frankly it would be worth looking at all the places where SpamBayes saves files, because this is probably not a pickle-specific issue. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com _______________________________________________ spambayes-dev mailing list spambayes-dev@python.org http://mail.python.org/mailman/listinfo/spambayes-dev
