I am currently attempting to involve myself more into Django
development. Have little to no idea how.
This seems to me like an easy pickings and I would be willing to port
existing code to the new package, if that's okay with the core team.
My expected approach:
1. verify claims
2. take the ticket
3. read up on the contribution guidelines
4. start with master, replace all memcached references with the new
library, possibly with minimal API impact
5. backport to 2.x, 1.x?
If this sounds remotely what's supposed to be done, let me know, I will
start working on it.
LP,
Jure
P.S. My planned involvement should ultimately reach around 200 hours of
yearly investment, should I prove to be useful. All pending verification
and validation, of course. I don't even know if that's a measurable
quantity, but right now these are my mid-term plans.
On 25/11/2019 00:45, 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
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/4671b78d-722d-d343-1d1c-7df9826322ec%40gmail.com.
