tim_one@users.sourceforge.net writes:
> New program just to display pickle sizes. This makes clear that the
> copy_reg based C implementation is much more space-efficient in the
> end than the __getstate__/__setstate__ based Python implementation,
> but that 4-byte date objects still suffer > 10 bytes of overhead each
> no matter how many of them you pickle in one gulp.
Presumably there's a possibility of an optimization for pickling
homogeneous (i.e. all the same type) lists (in pickle.py, not here).
Hard to say whether it would be worth it, though.
Cheers,
M.
--
This is the fixed point problem again; since all some implementors
do is implement the compiler and libraries for compiler writing, the
language becomes good at writing compilers and not much else!
-- Brian Rogoff, comp.lang.functional
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