Opened 7 years ago
Closed 5 years ago
#29887 closed New feature (fixed)
Add support for pymemcache
| Reported by: | Adrian Turjak | Owned by: | Nick Pope | 
|---|---|---|---|
| Component: | Core (Cache system) | Version: | dev | 
| Severity: | Normal | Keywords: | pymemcache | 
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no | 
| Needs tests: | no | Patch needs improvement: | no | 
| Easy pickings: | no | UI/UX: | no | 
Description (last modified by )
With python-memcached no longer getting any true support(1), maybe it's time django adds support for pymemcache(2)?
1: https://github.com/linsomniac/python-memcached/issues/95
2: https://github.com/pinterest/pymemcache
Change History (14)
comment:1 by , 7 years ago
| Description: | modified (diff) | 
|---|
comment:2 by , 7 years ago
| Component: | Uncategorized → Core (Cache system) | 
|---|---|
| Resolution: | → needsinfo | 
| Status: | new → closed | 
| Summary: | support for pymemcache to replace python-memcached → Add support for pymemcache to replace python-memcached | 
comment:3 by , 7 years ago
Mailing list thread started here:
https://groups.google.com/forum/#!topic/django-developers/PAiLQybcGT8
comment:4 by , 7 years ago
| Resolution: | needsinfo | 
|---|---|
| Status: | closed → new | 
| Summary: | Add support for pymemcache to replace python-memcached → Add support for pymemcache | 
| Triage Stage: | Unreviewed → Accepted | 
The initial response on the mailing list is positive.
comment:5 by , 7 years ago
| Owner: | changed from to | 
|---|---|
| Status: | new → assigned | 
comment:6 by , 7 years ago
I'm a maintener of https://github.com/django-pymemcache/django-pymemcache
Some API are different from python-memcache and pymemcache.
So I override pymemcache.HashClient and override some method to support python-memcached's API
comment:7 by , 7 years ago
@Maina Nick
Any progress on this? At the very least marking the backend as deprecated because the library itself is?
@Kosei Kitahara
That is always good to know, but I think ultimately if we supported this we're best writing a new standalone backend so that it uses the client natively and isn't reliant on the other backend which we should deprecate.
comment:8 by , 5 years ago
| Owner: | removed | 
|---|---|
| Status: | assigned → new | 
comment:9 by , 5 years ago
| Has patch: | set | 
|---|---|
| Keywords: | pymemcache added | 
| Owner: | set to | 
| Status: | new → assigned | 
| Type: | Cleanup/optimization → New feature | 
You should make this proposal on the DevelopersMailingList. If there's consensus, we'll reopen the ticket.