Opened 17 years ago
Closed 14 years ago
#6463 closed (wontfix)
Document that cmemcache has bug with floats (was: cache.get_many() returns garbage in case of floats (?) using memcached backend)
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Core (Cache system) | Version: | dev |
Severity: | Keywords: | cache, memcached, get_many, wrong results | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Memcached backend (using cmemcache 0.91 and libmemcache 1.4.0.rc2):
"ck" key of cache has been set to INTEGER and "ckt" to time.time():
cd = cache.get_many([ck, ckt]) hits, timeout = cd[ck], cd[ckt] print hits, timeout hits = cache.get(ck) timeout = cache.get(ckt) print hits, timeout
Output:
2 GAÑæ±ò6X.
2 1201326024.84
Change History (5)
comment:1 by , 17 years ago
comment:3 by , 17 years ago
Yes, seems like.
I've added this one with a small (temporary) Documentation change in mind - the Docs should mention this, instead of only saying cmemcache is faster than python-memcached.
comment:4 by , 17 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Summary: | cache.get_many() returns garbage in case of floats (?) using memcached backend → Document that cmemcache has bug with floats (was: cache.get_many() returns garbage in case of floats (?) using memcached backend) |
Triage Stage: | Unreviewed → Accepted |
Ok. Updating the ticket to reflect this, thanks :)
comment:5 by , 14 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
cmemcache is currently deprecated, and being removed in 1.4
Note:
See TracTickets
for help on using tickets.
After some tests I found out that this bug doesn't happen when using python-memcached instead of cmemcache.