Yes, you are right. But I asked for another reason. For example, I see, that werkzeug's cache write cache trough temporary file https://github.com/mitsuhiko/werkzeug/blob/master/werkzeug/contrib/cache.py#L660 But Django cache do not use neither, tmp file or file locking. So, multiple processes can write a file simultaneously. Also, other processes can obtain incomplete data.
I think it's a bug, so I asked a question in this group (django-developers). четверг, 28 марта 2013 г., 0:55:20 UTC+2 пользователь Russell Keith-Magee написал: > > > You've already asked this on django-users. Django-developers is for > discussing the development of Django itself -- it shouldn't be used as > "second tier" support if you don't get the answer you want on django-users. > > Yours, > Russ Magee %-) > > On Wed, Mar 27, 2013 at 8:16 PM, Ivan <[email protected] <javascript:>>wrote: > >> Hi all. >> Can anyone tell, does django.cache locks file for writing by concurrent >> process? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to >> [email protected]<javascript:> >> . >> Visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Django developers" 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]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
