On Thu, Mar 15, 2012 at 9:48 PM, Tres Seaver <tseaver at palladion.com> wrote: > On 03/13/2012 06:49 PM, Nick Coghlan wrote: >> On Wed, Mar 14, 2012 at 8:08 AM, Guido van Rossum <guido at python.org> >> wrote: >>> If you can solve your problem with a suitably hacked Unpickler >>> subclass that's fine with me, but I would personally use this >>> opportunity to change the app to some other serialization format >>> that is perhaps less general but more robust than pickle. I've been >>> bitten by too many pickle-related problems to recommend pickle to >>> anyone... >> >> It's fine for in-memory storage of (almost) arbitrary objects (I use >> it to stash things in a memory backed sqlite DB via SQLAlchemy) and >> for IPC, but yeah, for long-term cross-version persistent storage, >> I'd be looking to something like JSON rather than pickle. > > Note the Zope ecosystem (including Plone) is an *enoromous* installed > base[1] using pickle for storage of data over many years and multiple > versions of Python: until this point, it has always been possible to > arrange for old pickles to work (e.g., by providing aliases for missing > module names, etc.). > > ]1] tens of thousands of Zope-based sites in production, including very > high-profile ones: http://plone.org/support/sites Don't I know it. :-) So do you need any help porting to Python 3 or not? The OP didn't mention Zope. -- --Guido van Rossum (python.org/~guido)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4