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.
--
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-develop...@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.
A backport probably isn't needed, but I strongly urge
deprecation. The library has had a few failed attempts at pick up,
but ultimately those who wanted to do that just moved to
pymemcached, and anyone else sensible will do the same. There is
no need or want to maintain python-memcached when a strong
opensource alternative exists that is backed by pintrest. I
reached out to some of the people who were looking at picking up
maintaining it, but they never got any response back from the
current project owner, and going through the hassle of getting it
from them via pypi admins is a waste of time when pymemcached is
the clear winner in the pure python memcached library space.
python-memcached is dead for all intents and purposes, and with no
release since Dec 16, 2017 is in a bad place for us to not
deprecate. As such, this is bad for us, and looks bad for Django
that we still recommend this library as the first option when
using memcached.
--
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-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ce2804d3-8e41-4105-bcd3-0860e26b24e8%40googlegroups.com.
--
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-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/350ef193-5e90-4bfc-a224-5910c6669a4en%40googlegroups.com.