Opened 4 weeks ago
Closed 4 weeks ago
#37040 closed Bug (wontfix)
pylibmc and pymemcache suggested for Memcached cempletely outdated
| Reported by: | GirlThatLovesToCode | Owned by: | |
|---|---|---|---|
| Component: | Documentation | Version: | 6.0 |
| Severity: | Normal | Keywords: | |
| Cc: | MANAS MADESHIYA | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Django documentation shows Memcached as the best option for cache server. For Memcached binding, it suggests pylibmc and pymemcache as only options. They were both last updated in 2022 and the latest Python they officially support is 3.10.
I think pylibmc and pymemcache mentiones should be removed from the docs and there should be a note added, that there's no maintained bindings.
Also, I suggest moving Redis to the first spot. redis-py is actively maintained and widely used in production. It makes more sense as the recommended starting point than Memcached given the current state of the available bindings.
URL to the relevant part of the docs: https://docs.djangoproject.com/en/6.0/topics/cache/#memcached
Change History (2)
comment:1 by , 4 weeks ago
| Cc: | added |
|---|
comment:2 by , 4 weeks ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Refs #36153 and #35166
I don't believe it says this. Memcached just happens to be documented first. Is that what you mean?
I think the next steps would be to add your thoughts to the current forum thread: https://forum.djangoproject.com/t/should-we-stop-recommending-pylibmc/42993
We won't make changes until we reach a consensus on what direction to take