Prevents users from doing concurrent editing in Django. Works out of the box in the admin interface, or you can integrate it with your own apps using a public API.
Python JavaScript
Latest commit 8029a5c Feb 15, 2012 @debrouwere Point to Rob Combs' repo
Failed to load latest commit information.
docs Updated the changelog. Feb 4, 2011
locking Added version flag. Feb 18, 2011
.gitignore Got the tests running... and failing :-) Jun 2, 2010
LICENSE On branch master Jun 1, 2010
README Point to Rob Combs' repo Feb 15, 2012
setup.py Added version flag. Feb 18, 2011

README

New maintainer and repo
-----------------------

This repository is out of date. Find the new authoritative repo at https://github.com/RobCombs/django-locking

What the heck is this?
----------------------

Django has seen great adoption in the content management sphere, especially among the newspaper crowd. One of the trickier things to get right, is to make sure that nobody steps on each others toes while editing and modifying existing content. Newspaper editors might not always be aware of what other editors are up to, and this goes double for distributed teams. When different people work on the same content, the one who saves last will win the day, while the other edits are overwritten.

`django-locking` provides a system that makes concurrent editing impossible, and informs users of what other users are working on and for how long that content will remain locked. Users can still read locked content, but cannot modify or save it.

Documentation
-------------

django-locking is fairly well-documented. Check out the docs!

License
-------

django-locking comes with a simplified BSD license, see the included LICENSE file for details.