Update setup_databases call to handle >3.1 #859
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #858
A breaking change in the current master on Django has added a mandatory
time_keeper
kwarg to thedjango.test.utils.setup_databases
function signature. This is aTimeKeeper
object which is used to record how long it takes to setup test databases. It is used internally by the Django tests themselves. ANullTimeKeeper
object is available if timings are not required. I have used theNullTimeKeeper
in this PR (as I don't think setup timing is a core pytest requirement?)There are no additional tests for this change, as its main impact is in fixing the existing test suite. There should be a reduction in the number of current failures on
py*_djmaster
builds. I currently get these failures when runningmake test
locally against the latest master of Django: