#20536: File based cache is not safe for concurrent processes
-------------------------------------+-------------------------------------
Reporter: jaap3 | Owner: nobody
Type: Bug | Status: new
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution:
Keywords: filebasedcache | Triage Stage:
concurrency unicodeerror | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jaap3):
I've created a pull request that should fix this issue
(https://github.com/django/django/pull/1360)
I borrowed some code from django.contrib.sessions.backends.file as that
one has already been made safer.
Haven't done anything about _cull: but if anyone is interested there's
also ticket #15825 (File-based caching doesn't cull truly randomly)
--
Ticket URL: <https://code.djangoproject.com/ticket/20536#comment:2>
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/063.531ce41e0aef13a838531db8dbfc1e78%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
