#22606: Locmemcache has_key fails when cache expiry is None (infinite)
-------------------------------------+-------------------------------------
Reporter: boxm | Owner: Claude
Type: Bug | Paroz <claude@…>
Component: Core (Cache system) | Status: closed
Severity: Normal | Version: master
Keywords: | Resolution: fixed
Has patch: 1 | Triage Stage: Accepted
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: new => closed
* owner: => Claude Paroz <claude@…>
* resolution: => fixed
Comment:
In [changeset:"66880e4cd128ea81ae53ac6f292f00c563521009"]:
{{{
#!CommitTicketReference repository=""
revision="66880e4cd128ea81ae53ac6f292f00c563521009"
Fixed #22606 -- Locmemcache has_key() failed for infinite cache expiry
Refactored cache expiry logic for Locmemcache to make consistent across
all places where accessed, and correctly handle None as expiry time.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22606#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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.d3132b816c6f61c62af7267bed6e9737%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
