OBS: You'll need to resync/rebuild your database!

- This implements an updated, clearer and more robust access system. The policy is now to lock that which is not explicitly left open.
- Permission strings -> Lock strings. Separating permissions and locks makes more sense security-wise
- No more permissiongroup table; permissions instead use a simple tuple PERMISSIONS_HIERARCHY to define an access hierarchy
- Cleaner lock-definition syntax, all based on function calls.
- New objects/players/channels get a default security policy during creation (set through typeclass)

As part of rebuilding and testing the new lock/permission system I got into testing and debugging several other systems, fixing some
outstanding issues:
- @reload now fully updates the database asynchronously. No need to reboot server when changing cmdsets
- Dozens of new test suites added for about 30 commands so far
- Help for channels made more clever and informative.

src/objects/tests.py

@@ -28,6 +28,7 @@ from django.conf import settings
 from src.objects import models, objects
 from src.utils import create
 from src.commands.default import tests as commandtests
+from src.locks import tests as locktests
 
 class TestObjAttrs(TestCase):
     """
@@ -55,4 +56,5 @@ def suite():
     tsuite = unittest.TestSuite()
     tsuite.addTest(unittest.defaultTestLoader.loadTestsFromModule(sys.modules[__name__]))
     tsuite.addTest(unittest.defaultTestLoader.loadTestsFromModule(commandtests))
+    tsuite.addTest(unittest.defaultTestLoader.loadTestsFromModule(locktests))
     return tsuite