#9433: File locking broken on AFP mounts
-------------------------------------+-------------------------------------
     Reporter:  rndblnch             |                    Owner:  anonymous
         Type:  Bug                  |                   Status:  new
    Component:  File                 |                  Version:  master
  uploads/storage                    |               Resolution:
     Severity:  Normal               |             Triage Stage:  Accepted
     Keywords:                       |      Needs documentation:  0
    Has patch:  1                    |  Patch needs improvement:  1
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by rndblnch):

 Replying to [comment:15 dokterbob]:
 > The problem is confirmed to (still) exist in the master branch (e369dc)
 using the test code above, on OS X 10.6.8.
 >
 > However, the error is thrown regardless of whether the patch is applied
 or not.

 that is because the patch does not fix the bug per it-self.
 it just allows the client code to provide an alternative implementation to
 django.core.files.locks which is used by default by the
 django.core.files.storage module.
 fixing locks it-self for AFP volumes was not considered an option at the
 time (4 years ago).

 see comment:5 for a summary of the discussion + how to fix (read "ignore")
 the bug from client code once the patch is applied.

 >
 > A fork with the patch applied lives on my GitHub account:
 https://github.com/dokterbob/django/tree/ticket_9433

-- 
Ticket URL: <https://code.djangoproject.com/ticket/9433#comment:16>
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].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to