#22845: Memcached backend handles infinite (None) timeout defined in default
settings improperly
-------------------------------------+-------------------------------------
Reporter: Althalus | Owner: nobody
Type: Bug | Status: new
Component: Core (Cache system) | Version: master
Severity: Release blocker | Resolution:
Keywords: cache, memcached | Triage Stage:
Has patch: 1 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Althalus):
* needs_better_patch: => 0
* has_patch: 0 => 1
* severity: Normal => Release blocker
* needs_tests: => 0
* needs_docs: => 0
Comment:
In django 1.6 docs there's no information about infinite (`None`) cache
timeout (though code to use it was already delivered).
While in 1.7 it's described properly so I think we can consider it as a
new feature. Assuming that this ticket should be a release blocker.
[https://docs.djangoproject.com/en/1.7/topics/cache/#cache-arguments].
Also I've made a small and quite straightforward pull request:
https://github.com/django/django/pull/2817
On my current project that patch worked as expected.
--
Ticket URL: <https://code.djangoproject.com/ticket/22845#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.21fa0290e3b920993dedd4de81ba26c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
