#37106: pylibmc install fails from tests requirements on Python 3.12+ without
libmemcached installed
-------------------------------------+-------------------------------------
Reporter: Kiko Barr | Owner: Jason
Type: | Judkins
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 6.0
Severity: Normal | Resolution:
Keywords: test, pylibmc | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
Replying to [comment:9 Tim Schilling]:
> The person who had offered to help maintain pylibmc has started
maintaining a fork until activity resumes:
https://pypi.org/project/pylibmc2/
Let's keep the discussion about what to do about pylibmc in general to the
[https://forum.djangoproject.com/t/should-we-stop-recommending-
pylibmc/42993 forum thread], but I take the point that with over a dozen
people finding it a nontrivial research project to figure out how to
install it, it's not a good sign.
----
Tim G's suggestion in comment:6 is a good compromise given our general
stance against vendoring install instructions for packages (#29405).
Contributors are unlikely to need the cache libraries, as the tests are
skipped anyway unless you add pylibmc in your settings file, and most
sprint contributors are using test_sqlite.py, which does not configure any
caches.
Kiko, are you up for a tiny docs tweak to suggest commenting out
requirements pertaining only to tests that do not run under the default
test_sqlite.py configuration, or something like that?
Or even supplementing the advice to search the web with "or the Django
forum"? (Here is the [https://forum.djangoproject.com/t/error-when-
installing-requirements-for-django-tests-fatal-error-libmemcached-
memcached-h-file-not-found-include-libmemcached-memcached-h/1685/8
solution] that ought to be marked as the "solution" IMO.) Sounds obvious,
but since this was not a Django issue, my first search did not include
"Django Forum", so I found mostly garbage. (Apparently I still Google like
it's 2015...)
--
Ticket URL: <https://code.djangoproject.com/ticket/37106#comment:10>
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/0107019e92ec0253-4dc5498e-ecb4-4a98-ada7-9e704c5ed8c0-000000%40eu-central-1.amazonses.com.
