Ok, did all that. guardian does some "creative" things, am surprised it works under any version of Django. e.g. defining conflicting DB models, and only use one of them.
Next error:
Traceback (most recent call last):
File "setup.py", line 54, in <module>
**extra_kwargs
File "/usr/lib/python2.7/distutils/core.py", line 152, in setup
dist.run_commands()
File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 137, in run
self.with_project_on_sys_path(self.run_tests)
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 117, in with_project_on_sys_path
func()
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 146, in run_tests
testLoader = loader_class()
File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
self.parseArgs(argv)
File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
self.createTests()
File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
self.module)
File "/usr/lib/python2.7/unittest/loader.py", line 128, in loadTestsFromNames
suites = [self.loadTestsFromName(name, module) for name in names]
File "/usr/lib/python2.7/unittest/loader.py", line 113, in loadTestsFromName
test = obj()
File "/home/brian/tree/debian/unstable/django-guardian/django-guardian-1.2.4/tests.py", line 46, in main
failures = run_tests(settings)
File "/home/brian/tree/debian/unstable/django-guardian/django-guardian-1.2.4/tests.py", line 42, in run_tests
AFAIK admin == django.contrib.admin, not sure why it says it depends on testapp. Might be related to this inside testapp/migrations/0001_initial.py (django1.7 migration, not south):
AUTH_USER_MODEL="testapp.CustomUser", where testapp/models.py has a CustomUser class that is based on AbstractUser. Have a suspicion this might be somehow involved.