Feature request: Right now limpyd initializes all Redis collections with decode_responses=True which makes it impossible to store raw binary data (which raw Redis can do, and is useful for things like images and audio). My workaround for this for the time being has been to fork limpyd, turn this off, and just decode things by hand when they are string values instead of binary values.
But in the longer term, it seems like it might make more sense to have two different kinds of fields, like a StringField and a BytesField, which are identical from Redis's perspective, but where StringField's getters are automatically decoded by limpyd, and BytesField's getters are not. Is this something that you might be interested in supporting in the future? Or is there already a way for limpyd to deal with binary data that I am missing?
Feature request: Right now limpyd initializes all Redis collections with
decode_responses=Truewhich makes it impossible to store raw binary data (which raw Redis can do, and is useful for things like images and audio). My workaround for this for the time being has been to fork limpyd, turn this off, and just decode things by hand when they are string values instead of binary values.But in the longer term, it seems like it might make more sense to have two different kinds of fields, like a
StringFieldand aBytesField, which are identical from Redis's perspective, but whereStringField's getters are automatically decoded by limpyd, andBytesField's getters are not. Is this something that you might be interested in supporting in the future? Or is there already a way for limpyd to deal with binary data that I am missing?