#35770: Improve recommendation for ignoring memcached-incompatible cache key
warnings
-------------------------------------+-------------------------------------
Reporter: Markus Amalthea | Owner: Aditya
Magnuson | Chaudhary
Type: | Status: assigned
Cleanup/optimization |
Component: Core (Cache system) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aditya Chaudhary):
So, Is this right for the changes. Should I proceed with it ?
``If you are using a caching backend that accepts a wider range of keys
(e.g., a custom backend or one of the non-Memcached built-in backends) and
you prefer to suppress these warnings, you can do so with the following
code. This code can be added to the ready() method of an AppConfig class
in one of your INSTALLED_APPS, which is a more integrated and commonly
used approach:``
--
Ticket URL: <https://code.djangoproject.com/ticket/35770#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701920718841f-56da10f0-fbae-47d9-87da-99aacfb1725b-000000%40eu-central-1.amazonses.com.
