[Python-Dev] [ 654866 ] pickle and cPickle not equivalent (original) (raw)
Steve Holden sholden@holdenweb.com
Wed, 18 Dec 2002 15:17:51 -0500
- Previous message: [Python-Dev] [ 654866 ] pickle and cPickle not equivalent
- Next message: [Python-Dev] [ 654866 ] pickle and cPickle not equivalent
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Here is another thought that might outway the performance concerns: for > whatever reason, all instances of new-style classes (even with refcount > == 1, or perhaps because they don't have a refcount == 1) are getting > put in the cPickle memo.
Pickling of new-style classes is currently done using a Python helper. I am still hoping that I'll be able to dig myself out of the pile of Zope work that I'm currently under, and then I'd like to work on making pickling of new-style classes a lot more efficient. So please don't use this argument to cripple pickle any further.
I'm not a crippled pickle, I'm a crippled pickle's son and I'll be finished crippling pickles when the pickle crippling's done.
Sorry. Been working too hard ...
Steve Holden http://www.holdenweb.com/ Python Web Programming http://pydish.holdenweb.com/pwp/ Bring your musical instrument to PyCon! http://www.python.org/pycon/
- Previous message: [Python-Dev] [ 654866 ] pickle and cPickle not equivalent
- Next message: [Python-Dev] [ 654866 ] pickle and cPickle not equivalent
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]