| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
As the first target of the new .init. submodule move
celery_setup there. Quite straight forward, just a lot of
places to change.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
There's no real reason to support setting the celery config section;
so we'll just make it always ['celery'].
|
|
|
|
|
|
|
| |
These simply aren't needed any more, not now that the config validator
stuff does type conversion for us.
Also fixed the docstring to explain force_celery_always_eager.
|
|
|
|
|
|
|
|
| |
When running in celery-eager mode, the celery machinery
hides all exceptions inside "celery tasks" (you can find
out about them on the task handle somehow). Currently much
better to propagate them straight up, so they're visible on
the console.
|
|
|
|
|
|
| |
don't have to run celeryd at the same time.
This should make Elrond happy ;)
|
| |
|
| |
|
| |
|
| |
|
|
|