#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.

-- 
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/0107019d9a1b5213-a32e21d2-2ef3-4e82-8821-3ea682592780-000000%40eu-central-1.amazonses.com.

Reply via email to