[Python-Dev] PEP 574 (pickle 5) implementation and backport available (original) (raw)
Nathaniel Smith njs at pobox.com
Fri May 25 20:13:03 EDT 2018
- Previous message (by thread): [Python-Dev] PEP 574 (pickle 5) implementation and backport available
- Next message (by thread): [Python-Dev] PEP 574 (pickle 5) implementation and backport available
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, May 25, 2018 at 3:35 PM, Neil Schemenauer <nas-python at arctrix.com> wrote:
This discussion can easily lead into bikeshedding (e.g. relative merits of different compression schemes). Since I'm not volunteering to implement anything, I will stop responding at this point. ;-)
I think the bikeshedding -- or more to the point, the fact that there's a wide variety of options for compressing pickles, and none of them are appropriate in all circumstances -- means that this is something that should remain a separate layer.
Even super-fast algorithms like lz4 are inefficient when you're transmitting pickles between two processes on the same system – they still add extra memory copies. And that's a very common use case.
-n
-- Nathaniel J. Smith -- https://vorpus.org
- Previous message (by thread): [Python-Dev] PEP 574 (pickle 5) implementation and backport available
- Next message (by thread): [Python-Dev] PEP 574 (pickle 5) implementation and backport available
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]