# Should we stop recommending pylibmc?

**URL:** <https://forum.djangoproject.com/t/should-we-stop-recommending-pylibmc/42993>\
**Category:** Documentation\
**Created:** [September 26, 2025, 12:47pm UTC](https://forum.djangoproject.com/t/should-we-stop-recommending-pylibmc/42993 "2025-09-26T12:47:27Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![jacobtylerwalls](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/jacobtylerwalls/32/30603_2.png) [@jacobtylerwalls](https://forum.djangoproject.com/u/jacobtylerwalls)\
**Post date:** [August 19, 2026, 4:40pm UTC](https://forum.djangoproject.com/t/should-we-stop-recommending-pylibmc/42993/7 "2026-08-19T16:40:32Z")

</div>

That fork is only five commits ahead of the upstream fork, with a bunch of release tooling updates. At a glance, it doesn’t look like there’s anything shady there, but it would be nice to know of folks using it in production and verifying that’s it’s not malware before we recommend it.

We should do something before the Django 7.0 branch is cut in January. If no one can vouch for `pylibmc2`, I think we need to deprecate all of the memcached clients, and we should do that in Django 6.2.

---

_[View the full topic](https://forum.djangoproject.com/t/should-we-stop-recommending-pylibmc/42993)._