Open charlesdaniels opened 6 years ago
Closed https://github.com/charlesdaniels/bitshuffle/issues/44 so this is good to go :)
Excellent.
Hopefully I will have time soon. Perhaps this weekend.
On Feb 19, 2018, at 5:39 PM, Joshua Nelson notifications@github.com wrote:
Closed #44 so this is good to go :)
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.
The format in which BitShuffle stores encoded data needs to be finalized. With the closure of #46, this should basically involve codifying the current BitShuffle behavior in a formal document and adding tests which assert future versions can decode packets from the current version. This can be accomplished by encoding a known magic string with the current BitShuffle version and having a test case which decodes it and asserts it is identical to the original string.