#18541: Infinite Lock With Caching Backend
-------------------------------------+------------------------------------
Reporter: zmsmith | Owner: nobody
Type: Bug | Status: new
Component: Core (Cache system) | Version: 1.4
Severity: Normal | Resolution:
Keywords: caching | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Changes (by aaugustin):
* needs_better_patch: => 1
* component: Uncategorized => Core (Cache system)
* needs_tests: => 0
* needs_docs: => 0
* type: Uncategorized => Bug
* stage: Unreviewed => Accepted
Comment:
Historically, a one-liner put in the cache a deepcopy of the object. Later
deepcopy was replaced by pickle, and the code was refactored to split the
two operations:
- creating acopy of the object
- storing it in the cache
Only the second part needs to be thread-safe. I agree with the change.
An test that hangs infinitely isn't helpful. Maybe we could put a timeout
with [http://docs.python.org/library/signal#signal.alarm signal.alarm()]?
Any better ideas?
--
Ticket URL: <https://code.djangoproject.com/ticket/18541#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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
