Force ordering of settings and transactional_db fixtures #870

[bdauvergne]

Fixes #870.

[bluetech]

Thanks for the PR, I understand the issue now, and the change LGTM.

I suggested a comment, and this also needs a rebase against the latest master. Afterwards, if the CI is green, we can merge.

[bluetech]

I suggest adding a comment explaining the rationale:

Suggested change

	if 'transactional_db' in request.fixturenames:
	# Order the `settings` fixture after DB.
	# We don't want overridden settings to be in effect during
	# DB setup/teardown/post_migrate.
	if 'transactional_db' in request.fixturenames:

[bdauvergne]

Tests failures seem to be the same than on master, with djmain.