#36153: Remove or replace unmantained pylibmc package from Django dependencies
-------------------------------------+-------------------------------------
     Reporter:  Paolo Melchiorre     |                    Owner:  (none)
         Type:  Bug                  |                   Status:  new
    Component:  Core (Cache system)  |                  Version:  dev
     Severity:  Normal               |               Resolution:
     Keywords:  memcached, pylibmc,  |             Triage Stage:
  package                            |  Someday/Maybe
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Paolo Melchiorre):

 Replying to [comment:1 Sarah Boyce]:
 > * I can see in 19c4052f98e5dc4fe9d7edd7125df6a66efbd79f as part of
 adding Python 3.12 support, we install `libmemcached-dev`. This doesn't
 appear to be documented and we possibly need to document this.

 Yes, that's the same advice I gave to  Daniele Varrazzo in the psycopg
 issue: https://github.com/psycopg/psycopg/issues/999

 > * I think the decision to remove `pylibmc` is a decision to deprecate
 `PyLibMCCache`, this is still used
 
[https://github.com/search?q=%22django.core.cache.backends.memcached.PyLibMCCache%22+language%3APython&type=code
 quite a bit] from what I can tell. I can't imagine that would be a popular
 decision

 I can image it, but the project seem abandoned and we remove dependencies
 in the past after a period of deprecation.

 > Generally, I think this needs quite a lot of input before a decision can
 be made (and probably a Django forum discussion).

 Ok, I can open a thread in the forum if you think it will help having more
 feedback on it.

 > Django 6.0 is due to be released until December so there's quite some
 time for a release to `pylibmc` to be issued. Will mark as `Someday/Maybe`
 to revisit closer to that date.

 I'm a bit pessimistic on that point because Daniele itself opened an issue
 to request a new pylibmc  release compatible with Python 3.12 long time
 ago without any answer:
 https://github.com/lericson/pylibmc/issues/288
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36153#comment:2>
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/01070194b19d10a4-899a3d00-086d-4586-92c0-8760dd965da0-000000%40eu-central-1.amazonses.com.

Reply via email to