After doing some refactoring on how some of the badges imports are done to break out of python import loop suck, I hit another small obstacle in the form of guardian requiring mock for its built in user tests. (See https://github.com/lukaszb/django-guardian/issues/184) Installing mock gets me further; do we want to just follow the guardian approach of documenting that mock is needed to run tests (note also that so far at least, if I just use django manage.py test core I don't get that issue, in other words this appears to only be if we want to run the guardian included unit tests at the moment)
After doing some refactoring on how some of the badges imports are done to break out of python import loop suck, I hit another small obstacle in the form of guardian requiring mock for its built in user tests. (See https://github.com/lukaszb/django-guardian/issues/184) Installing mock gets me further; do we want to just follow the guardian approach of documenting that mock is needed to run tests (note also that so far at least, if I just use django manage.py test core I don't get that issue, in other words this appears to only be if we want to run the guardian included unit tests at the moment)