| | Bump django dependency to 1.6 |
| |
|
| | This change updates our django dependency to >= 1.6.1. |
| |
|
~ | | The bulk of this change is to make sure that we call initialize() inside our
|
~ | | test case setup function. It turns out that the test Client.login() method no
|
~ | | longer uses a request, which means that our middleware that loads the
|
~ | | siteconfig isn't guaranteed to run. For one of our tests, it was hitting the
|
~ | | case that the user would be authenticated against ModelBackend, and then when
|
~ | | we tried to do an actual request, it would load the siteconfig, replacing
|
~ | | settings.AUTHENTICATION_BACKENDS . Once this happened, it would check that
|
~ | | user.backend was in the loaded backends, and when it wasn't, set request.user
|
| ~ | With the previous change to make sure that initialize() is called from test
|
| ~ | setUp() methods, this is pretty small:
|
| ~ | * Update the hg and bzr tests to properly detect missing dependencies and skip
|
| ~ | tests as appropriate.
|
| ~ | * Remove the django.contrib.markup app. We got rid of our usage of this a while
|
| ~ | ago and forgot to remove it from INSTALLED_APPS . In Django 1.6 it's been
|
| ~ | removed entirely.
|
| ~ | * Change the setup.py check to reject Python 2.6 versions less than 2.6.5. |
- | | to be AnonymousUser . |
- | |
|
- | | I've solved this issue by calling initialize() inside TestCase.setUp() . A lot
|
- | | of our TestCase subclasses weren't calling the super class' setUp() , so I've
|
- | | fixed that. |