Celery wasn't really being properly connected during tests.
authorChristopher Allan Webber <cwebber@dustycloud.org>
Sun, 26 Jun 2011 19:45:19 +0000 (14:45 -0500)
committerChristopher Allan Webber <cwebber@dustycloud.org>
Sun, 26 Jun 2011 19:45:19 +0000 (14:45 -0500)
commit9ea5c28b7a3bb74cebd923353b9e4c780e658d74
treedb6b94000136f160b703fbc1a2cb5a71a5cc1c8c
parent426685e088cd1867c12fc2721d2430e1be335297
Celery wasn't really being properly connected during tests.

Lots of fixes to do this.

 - setup_celery_from_config no longer responsible for checking
   'celery_setup_elsewhere'; that's the app's job.  (This was a problem
   because more than the app was relying on using this function)
 - Allow us to specifically set the config file we're setting up
   celery from with setup_self
 - Set up celery_always_eager.  This is something we strongly want
   while doing tests.
 - Instead of setting up the app in the get_test_app method, let's set
   that up simply by importing from_tests, which should itself up via
   from_celery being the environment variable being set.
mediagoblin/celery_setup/__init__.py
mediagoblin/celery_setup/from_celery.py
mediagoblin/celery_setup/from_tests.py
mediagoblin/tests/test_mgoblin_app.ini
mediagoblin/tests/tools.py