| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Thought I installed these... guess I didn't!
|
| |
|
|
|
|
|
| |
Some simple changes needed to do that.
The interesting question left:
Should config_spec.ini also be moved?
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Basically, if we don't do this celery sets itself up before it should
and improperly. :\
|
| |
|
|
|
|
|
|
|
| |
Lots of changes:
- CELERY_CONFIG_FILE does not need to be set to the from_tests module
to run tests anymore, in fact it *should not be set at all* and is
specifically forbidden.
- moved around the configuration to the new 2-file format
- and generally adjusting the code appropriately.
|
| |
|
|
| |
Setting test_register_views() to use it also.
|
| |
|
|
|
|
|
|
|
| |
of the paste config file the way paste would than to load components
of it ourselves.
Aside from this being nicer, it's also necessary for the sake of
getting the middleware working nicely. We could do it ourselves, but
why bother when paste can just do it for us?
|
| |
|
