If you're going to script a request, then you'll need to follow the
bootstrap/commandline/shell docs. That means loading your whole app and
tying into the request lifecycle.
I have some various commandline tasks that require me to run several tasks
though a pyramid environment.
To handle th
Good point about the debug_toolbar. That might be it. Thanks!
Any other celery examples out there? Especially around scripting requests?
Thanks,
Robin
2015-11-18 22:12 GMT+01:00 Jonathan Vanasco :
> Ok, this use case is somewhat similar to ours... in that it doesn't
> require pyramid at all.
Ok, this use case is somewhat similar to ours... in that it doesn't require
pyramid at all. We use sqlalchemy, but zodb shouldn't be much different.
We have 2 packages:
* `myapp_pyramid`
* `myapp_celery`
`myapp_pyramid` will import `myapp_celery` to call it's `@task` decorated
functions. the
Fair point :)
I have an application with a ZODB. Some parts of the app will require
complex calculations that will take a really long time to run. After they
finish, they'll want to write something. So i essentially imagine something
like this:
- Pyramid frontend, read access
- Celery long runnin
