I strongly second not breaking backwards compatibility and
interoperability, especially for persistent artifacts, unless there is a
*REALLY* good reason. A potential unintended side effect of such breakages
is that it slows down adoption of the new version.
-Peter
On Fri, Apr 26, 2019 at 10:27 A
I think it's better not to introduce a new opcode, for the reason you
stated -- you don't want your pickles to be unreadable by older Python
versions, if you can help it.
On Fri, Apr 26, 2019 at 5:59 AM Pierre Glaser
wrote:
> Hi All,
>
> We (Antoine Pitrou, Olivier Grisel and myself) spent some
Hi All,
We (Antoine Pitrou, Olivier Grisel and myself) spent some efforts recently on
enabling pickle extensions to extend the C-optimized Pickler instead of the
pure Python one.
Pickle extensions have a crucial role in many distributed computing libraries:
cloudpickle (https://github.com/cl
