- Add python 3.4 and Django 1.7 travis configuration. - Advertise python 3 and 3.4 in classifiers. - Advertise Django 1.7 support in README. - Rename test modules to start with 'test' for better consistency with unittest module and new Django test runner. - Explictly set TEST_RUNNER in test_project settings to avoid Django from throwing a warning. - Fix test_project/urls.py to work with absense of relative imports in python3.
…logout url and causing an infinite loop.
This adds the setting `STRONGHOLD_PERMISSIONS_DECORATOR`. `STRONGHOLD_PERMISSIONS_DECORATOR` allows the developer to define the decorator to use to define the behavior of Stronghold. The current behavior defaults to the login_required decorator. You could change this setting to staff_member_required and it would apply this to all non whitelisted or views marked public. Developers can also write their own decorator that requires any combination of permissions they desire here. Fixes #34 Thanks @andybak for the idea.
Use django-discover-runner to run tests in the case of Django version < 1.6 . Still a little hackish, but viable way to get the tests run for now. Update .travis yml to install new requirements before a test run, update makefile to run tests using discover runner and explicitly use the settings we have setup in the test project