Settings fixture + Celery

[dbrgn]

I'm trying to update the settings for Celery using the settings fixture (CELERY_ALWAYS_EAGER=True). But somehow celery fetches its settings before I get to the point where I update them, so changing the settings fixture has no effect.

This used to work with the Django test class: https://docs.djangoproject.com/en/dev/topics/testing/overview/#overriding-settings

Is there a fix or workaround to this problem?

[pelme]

Settings are tricky. :(

Django's override_settings does things in a slightly different way than the settings fixture.

It sets the _wrapped attribute on django.conf.settings. It also sends the setting_changed signal. I guess the most reliable way of doing this would be to use django's override_settings internally for the settings fixture, rather than just changing attributes on settings as is done now.

[dbrgn]

Yeah, I guess that would work better, because it would also continue to work when the internal implementation of override_settings changes.

[dbrgn]

What's the status of this? Do you think it would be easy to fix?

[brianz]

This is an old thread, but if you're ok with updating this setting for the entirety of your tests you can do:

# conftest.py

from django.conf import settings

def pytest_configure(config):
    setattr(settings, 'CELERY_ALWAYS_EAGER', True)

I'm using this and it works well so far.

[dbrgn]

@brianz Thanks, looks like a nice workaround. Getting the fixture to work would be even better though :)

[pelme]

I'm closing this in favor of #136 which tracks the improvements to the settings fixture.