traceback Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling needs. Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling time. If there are more open connections than max_pool_size, sockets will be closed when they are released. Defaults to 10. options Additional keyword arguments to pass to the mongodb connection constructor

traceback Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling needs. Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling time. If there are more open connections than max_pool_size, sockets will be closed when they are released. Defaults to 10. options Additional keyword arguments to pass to the mongodb connection constructor

traceback Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling needs. Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling time. If there are more open connections than max_pool_size, sockets will be closed when they are released. Defaults to 10. options Additional keyword arguments to pass to the mongodb connection constructor

traceback Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling needs. Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling time. If there are more open connections than max_pool_size, sockets will be closed when they are released. Defaults to 10. options Additional keyword arguments to pass to the mongodb connection constructor

traceback Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling needs. Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling time. If there are more open connections than max_pool_size, sockets will be closed when they are released. Defaults to 10. options Additional keyword arguments to pass to the mongodb connection constructor

traceback Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling needs. Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling accepted. When a branch is frozen the focus is on testing the version as much as possible before it is released. dev branch The dev branch (called “master” by git), is where development of the next version

traceback Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling needs. Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling accepted. When a branch is frozen the focus is on testing the version as much as possible before it is released. dev branch The dev branch (called “master” by git), is where development of the next version

traceback Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling needs. Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling accepted. When a branch is frozen the focus is on testing the version as much as possible before it is released. dev branch The dev branch (called “master” by git), is where development of the next version

time. If there are more open connections than max_pool_size, sockets will be closed when they are released. Defaults to 10. options Additional keyword arguments to pass to the mongodb connection constructor accepted. When a branch is frozen the focus is on testing the version as much as possible before it is released. master branch The master branch is where development of the next version happens. Maintenance col.html#version-2] to be introduced in Celery 4.0. Users upgrading to Celery 4.0 when this is released are encouraged to upgrade to this version as an intermediate step, as this means workers not yet

traceback Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling needs. Warning Backends use resources to store and transmit results. To ensure that resources are released, you must eventually call get() or forget() on EVERY AsyncResult instance returned after calling accepted. When a branch is frozen the focus is on testing the version as much as possible before it is released. dev branch The dev branch (called “master” by git), is where development of the next version