Raymond Hettinger <rhettin...@users.sourceforge.net> added the comment:
> A further version of the pickle protocol could > have a dedicated opcode for sets instead... -1 We don't have to introduce a new (and backwards incompatible) opcode for every possible container type. The space savings is miniscule (because you still need to list out the items). All that is saved is the enclosing list or tuple setup (five bytes in the case of sets). People concerned about pickle size would be much better off investing time into a more generic solution (such as adding a code to automatically run zip/gzip/bzip/xz etc). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9120> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
