[Django] #37040: pylibmc and pymemcache suggested for Memcached cempletely outdated

0 views
Skip to first unread message

Django

unread,
2:23 AM (4 hours ago) 2:23 AM
to django-...@googlegroups.com
#37040: pylibmc and pymemcache suggested for Memcached cempletely outdated
-------------------------------------+-------------------------------------
Reporter: GirlThatLovesToCode | Type: Bug
Status: new | Component:
| Documentation
Version: 6.0 | Severity: Normal
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
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
--
Ticket URL: <https://code.djangoproject.com/ticket/37040>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
5:26 AM (1 hour ago) 5:26 AM
to django-...@googlegroups.com
#37040: pylibmc and pymemcache suggested for Memcached cempletely outdated
-------------------------------------+-------------------------------------
Reporter: GirlThatLovesToCode | Owner: (none)
Type: Bug | Status: new
Component: Documentation | Version: 6.0
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by MANAS MADESHIYA):

* cc: MANAS MADESHIYA (added)

--
Ticket URL: <https://code.djangoproject.com/ticket/37040#comment:1>

Django

unread,
5:42 AM (1 hour ago) 5:42 AM
to django-...@googlegroups.com
#37040: pylibmc and pymemcache suggested for Memcached cempletely outdated
-------------------------------------+-------------------------------------
Reporter: GirlThatLovesToCode | Owner: (none)
Type: Bug | Status: closed
Component: Documentation | Version: 6.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):

* resolution: => wontfix
* status: new => closed

Comment:

Refs #36153 and #35166

> Django documentation shows Memcached as the best option for cache
server.

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
--
Ticket URL: <https://code.djangoproject.com/ticket/37040#comment:2>
Reply all
Reply to author
Forward
0 new messages