That's a tough question. It depends on when and how we do it. A new backend can potentially be backported to 2.2 (the current safe LTS), but we can't really update the existing one if people are using it and expect it to work. Django doesn't actually have any deps for these libraries, so people have to install them as part of their app deployment.
A new backend, even if mostly a copy of the old one, is the safer approach and then people need to actively switch to it, and be aware of it. We then deprecate the old one, and we can backport to 2.2 the new safe one, and remove the old one in never versions. On 25/11/19 11:05 pm, Johannes Hoppe wrote: > Do we actually need to deprecate the current backend and create a new > one? Can't we just rewrite the current backend? Technically changing a > dependency doesn't require deprecation, does it? It's also a very > simply update process. > > On Monday, November 25, 2019 at 6:46:05 AM UTC+7, Adrian Turjak wrote: > > A while ago now I opened a ticket that we need to deprecate the > python-memcached backend in Django, and ideally make a new one which > uses Pinterest's pymemcache instead (which is now the most > commonly used > one). > > This is the ticket: > https://code.djangoproject.com/ticket/29887 > <https://code.djangoproject.com/ticket/29887> > > But it seems there hasn't been any work on it. Someone assigned > themselves, but nothing beyond that has happened. > > At this stage we really need to remove the docs that recommend > python-memcached, and the backend associated with it, and say > officially > that only pylibmc is a valid and safe option from the core backends > using Memcached. > > Considering how important Memcached is to a lot of projects, this > ought > to be a high priority item, with some urgency given that Django > core is > sporting support for a now very deprecated and outdated library (Last > released: Dec 16, 2017), with no future, and a clear successor in > pymemcache. > > I'm sadly not in a position where I can contribute this myself, but > would be happy to test/review. Are there any willing contributors for > this? Or some people from the Django core team which will tackle > this? > > Cheers, > Adrian Turjak > > > > > -- > You received this message because you are subscribed to the Google > Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to django-developers+unsubscr...@googlegroups.com > <mailto:django-developers+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/a5eaf9cc-21aa-4cb8-9d61-9fc8e76e0733%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/a5eaf9cc-21aa-4cb8-9d61-9fc8e76e0733%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/28b2116b-6592-acfc-5726-68764676639f%40catalyst.net.nz.
