#36020: redis cache backend serializing floats
-------------------------------------+-------------------------------------
Reporter: amirreza | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Core (Cache system) | Version: 5.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* cc: Nick Pope (added)
* resolution: => wontfix
* status: new => closed
Comment:
In investigating this ticket, I found something on `django-redis` on
`incrbyfloat`: https://github.com/jazzband/django-
redis/issues/311#issuecomment-412816573
> [This] is not a redis client, [this] is a django cache backend. It
should implement the interface of django cache backend. If you want access
to redis funcionality you can access to redis connection directly using
http://niwinz.github.io/django-redis/latest/#_raw_client_access that
already exposes all redis functionality and we dont need reimplement it.
This sounds like a request to make it easier to interact with other redis
operations. I don't think that's the goal of the cache backend
--
Ticket URL: <https://code.djangoproject.com/ticket/36020#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070193d4fd08ce-0cc9799a-d6fe-4f3a-8be5-64c552ad5389-000000%40eu-central-1.amazonses.com.
