Closed BrunoBonacci closed 7 years ago
It seems that this incompatibility was introduced with this commit (tested via git bisect
)
commit 327a800d8010931558c624aaaaf7a7cc5751ca7d
Author: Peter Taoussanis <ptaoussanis@gmail.com>
Date: Mon Sep 28 16:38:48 2015 +0700
Experimental: optimize common case of small maps, sets, vectors
Hi Bruno,
I'm afraid the behaviour you're seeing is expected; Nippy is a versioned format and generally only promises to be forward-compatible.
Data frozen with Nippy version x is expected to be readable with Nippy version >= x. It appears that you're trying to go the other way round.
thanks for your clarification.
No problem, apologies if this wasn't clear from the documentation.
Hi,
if I encrypt a message using the latest nippy version (2.13.0), these messages are not readable by older versions of nippy (2.7.0) despite using the same compressor and encryptor.
example (with nippy-2.13.0)
However if I try to read this payload using nippy/2.7.0
Is this something we should expect or it is an unwanted behaviour? Is there a set of options which we can pass to
freeze
in order to produce encrypted messages which are readable by older nippy versions?